Saurabh1 Absent Member.
Absent Member.
669 views

Maintaining test cases in Test Plan while handling multiple released versions?

My project is supporting multiple versions for the clients (e.g. 10.x, 1.x, 12.x) and all are active versions. Once an issue is reported in one version (say 10x), then it is fixed through a task (Task A) within that version and then fixed is synced synced to other future/past versions (Task B, Task C). As a QA, when mainiting the test case for such a scenario, what should be the best practice that I can follow? Approaches that I can think of are:

Approach 1 - Have duplicate test cases in Test Plan for each version so that we are able to track the effort that happened in each release ?

Approach 2 - Have just 1 test case corresponsing to the version where it was found. For execution of that test case after a fix is made in a different release, pull the same test case from other version (10.x) and execute in Test Lab under 11.x version.

 

I am less inclined towards the Approach 2 as it hampers the test reporting, coverage etc

 

Please share your valuable inputs on the best practice to handle such situations. 

 

 

0 Likes
2 Replies
Chris_Grz Outstanding Contributor.
Outstanding Contributor.

Re: Maintaining test cases in Test Plan while handling multiple released versions?

Baselining (see this document ) may be another approach.

 

There is no one-size-fits-all solution. You have to review all solutions in your context. 

 

 

 

0 Likes
Absent Member.. BrendanDick Absent Member..
Absent Member..

Re: Maintaining test cases in Test Plan while handling multiple released versions?

How are you doing your reporting that Approach 2 will impact coverage etc? If your coverage is generated based on what you've scheduled/executed for a release/version there shouldn't be an impact. Typically, plan is organised based on process or function (at least for anything common, you might have some version specific tests temporarily if you are not useing baselines) and lab by release/version.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.