New answers tagged

0

You also may consider that the complex the test the more defects will be associated with it. My rule of thumb, and again context is important, is that a test should uncover one bug. The additional reason for thinking along these lines is that if you are going to automate your tests you want to be able to pinpoint quickly what the specific reason for the ...


0

In an Agile environment think of a test plan less in terms of a formal document and more as a conversation that sometimes will result in documentation, sometimes detailed, sometimes none. The key thing is to go over logic, conditions, exceptions and the like with the developer(s) before they start coding to both determine how to test the change and also ...


0

It's a good question although the answer is "it depends" until you define "better" The first way (1 test checks all assertions) is better for: more compact code quicker tests, only 1 setup needed easier to maintain tests quicker development The second way (1 test for each assertion) is better for: encouraging more specific and descriptive test and ...



Top 50 recent answers are included