In my experience, I am repeatedly finding that the proper mapping between
Test Case <==> Test Data <==> Test Environment <==> Bug

acting as a great tool for any tester / test team.

In other words, every bug should have its own test case/test data mapped.
In the same way, every test case (or test run) should have its test environment / test data / bug (if applicable) mapped.

It will help tester / test team in

1.High Rate of Reproducible bugs
2.Making the test process as resource independence
3.Transparency in testing
4.Getting a view on test coverage
5.Getting the Test case coverage ratio (No.of test cases Vs Total number of bugs)

Albeit, it seems to be so naive to read, but one of challenging tasks in any test team (inversely proportional to testing team size).

The problem starts when test team enters into hectic schedule of testing during the project. During and After this high concentrated testing, team gets exhausted for maintaining this mapping and concentrates more on 'after live' issues.

But even after two/three short releases when testing team gets little time for doing this exercise, unless team is highly disciplined, it is very difficult to carry this (mapping) exercise. Test Manager can easily use this mapping as a yardstick to measure the 'discipline' of testing team!

0 opinions: