Version control of all artifacts is important in any test management process. It doesn’t matter if you are using word, excel or a very clever bespoke application to track this information. Either way you must track changes made to records. The reason for this was highlighted recently when a supplier delivered a new software solution to a client. The client incurred some significant unexpected costs due to a defect in the software. As is usual in cases like this the project manage points the blame at the testing team. He demands to know why this defect wasn’t found during the validation and verification phase. Unhappy customer and an unhappy project manager. And, initially at least, an unhappy team wondering why they didn’t find such an obvious issue before release.
However, this team had a mature and effective test management process in place. They were able to quickly recreate the environment, product release and checks that should have found this defect. Good tracking of all these artifacts meant they could repeat this with confidence. In fact they could repeat this with exact versions of the artifacts that they used in the original setup.
Once the replication process was completed, the team was able to confidently show the client that the software was in fact, defect free. Once the facts were on the table, both parties were able to ascertain that it was because the client had the incorrect product in the first place. Even though the instructions on the packaging were crystal clear, someone was able to purchase, install and run the incorrect product, despite the straightforward installation directions.
It goes without saying that management breathed a sigh of relief that the error did not stand with the team. It also became apparent that the testing process that was in place was without flaws. Even though there was no admission of guilt, there was a fair amount of satisfaction from the project manager, as the team had met their goals successfully.
For the individual that designed this, it was an absolution of his conscientiousness and expertise that he could prove this. It’s a painful position for an employee to be in, when higher-ranking managers and consumers are looking to assign fault. It is even worse, when that team member has constantly delivered superior service, year after year. It does draw attention to the magnitude of a proficient test management system and superior control of all the objects used.
If you are a tester, could you with all honesty declare that in the event that all the cases and setups you create now could be completely recreated one year from now. Would you be able to pinpoint the exact location of the relevant information and elements required that you used previously. Would you be able to remember the exact element version that was used initially. Of course, you may need to know the precise release of the product being checked, as well as the cases. And it goes without saying that each and every version of each case used, will need to be located. As well as the arrangement and location you ran these elements on.
The most complex of these essentials, can be, administrating the cases. In one short year, all the cases one may have used could be unrecognizable. If you are unable to find the exact account that was previously used, it becomes abundantly clear that you do not have a duplicating process of testing management. It is very hard to incessantly follow the information daily. Definitely when on the odd occasion you may have to go back and use the information, it may very well seem like a wasted expense of effort and time. However, for those situations, you are going to really appreciate the time and hard work you put in, keeping detailed records and for having a sound test management procedure that keeps all the movements of the artifacts up to date.
Check out our website for details about the importance of version control in the test management process, now. You can also find information about the Test Complete software program at http://www.testmanagement.com today.