Test Dependencies

We make our tests as independent as we can.  Each one will create it's own data or read it from Excel, but it should not be relying on a previous test.  This works for data entry and calculations, so most unit test type things and some functional tests.

This can change when we get into workflow tests.  In this case, the dependency is sometimes part of the test.  The test might enter a bunch of things in one screen and then expect certain results in another screen.  In that case, if the first one is inaccurate, I want the second one to fail.  

For your example, if 3 is dependent on 2, but 2 fails, then would you still have the correct data for 3 to go on?

p.s.  Can I suggest another title for your post?  Something like "test dependencies" might be more helpful when others are searching the forum.  :)

I’m also facing same problem. As Marsha stated trying very hard to make each test independent.

The other strategy I’m using currently is concept of smoke test. It is a tiny subset of main test suite. Just after a build I run small sample of most critical tests. For example part of initial data inserting scrips, part of most critical flows test. So before night/weekend run I know whether critical tests are not broken environment is stable.

I learnt in a hard way, that test no 10 should not depend on result data of test no 05. Never reuse data. Now I’m trying hold separate data sets for each test. And you can do that with minimum changes to scripts. Particularly when using DDT.

Think most hard thing is to deal with system state. If test 04 change the state to run test 05 then you have lot of work ahead.

Hi,

Regardless of what test framework / tools / scripts you use having dependencies between tests is a fundamental No No !! All tests must be able to run independently and in any order. You have broken this rule an now you are paying and will contue to pay until you refactor your tests.

John