PROACTIVE ISSUES

Proactive ISSUES

I have wondered many times, why a tester doesn’t share their test scripts to developers. Yes, for the reason they read the possible cases of testing and can pass the issue for those cases.

This envisaged an idea, how this can be done to help in a right direction and for delivering a high quality product. There arise a thought like revealing certain cases to the developers before they submit for testing.

Like, when the issue has been first raised by the tester, the tester should also raise few more issues like linked temporary issues. Such that when the developer goes thought the issue would also have knowledge of the linked issues that might occur while fixing this issue. This proactive method though raises few more issues but if you look closer into the design, the closing up of issues will be fast and with very high quality than the previous.

Now, digging onto the core concept of Proactive Issues. As the analyst suggest for any change request, the request document is sent to both development team and test team. The development team starts the design process and the test team starts writing test scripts. Now as an extra effort, the test team should also write scripts for proactive issues and should straight away raise proactive issues in the issue tracker tool. Now the developer will get the design doc as well the set of proactive issues. Any developer who fixes the code will have an understanding on what are the possible issues and the fixed code will not raise any error now. If so any error occurred and issue has been raised, now the tester should not raise a single issue, he should also raise the link and supportive issues along with it.

This stringent process can avoid the delay of issue cycle rotation and will boost up the delivery date. This was Just a flash came to my mind when I was about to sleep.

Hope the industry experts will reply comments about the same.