Why does the Python unittest doc contradict itself?

Question

The Python unittest doc defines a test case as:

"[...] the smallest unit of testing. It checks for a specific response to a particular set of inputs."

However the first example contains a method with two assertions:

def test_shuffle(self):
    ...
    self.assertEqual(self.seq, range(10))
    ...
    self.assertRaises(TypeError, random.shuffle, (1,2,3))

This is clearly a contradiction, since the assertions each contain their own inputs and expected response.

Which approach is most appropriate?

en.wikipedia.org/wiki/Test_case

dylrei
– dylrei

2015-01-13 16:20:02 +00:00
Commented Jan 13, 2015 at 16:20 — dylrei
– dylrei, Commented Jan 13, 2015 at 16:20

Ned Batchelder · Accepted Answer · 2015-01-13 18:13:06Z

1

Having two assertions is not a problem in and of itself. But the first example in the docs does test two separate things, and should be split into smaller pieces.

The question of how finely to slice your tests can become a philosophical one. Find a balance that feels right to you.

answered Jan 13, 2015 at 18:13

Ned Batchelder

378k77 gold badges583 silver badges675 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why does the Python unittest doc contradict itself?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related