Best practice for managing test cases in AIO jira.

Manish Gowda

Hello team,
Presently we are grouping test case's folder wise for a respective release in Jira so that we have a history of cases added and removed in a particular release. But because of this we are facing issues like jira takes too much time to load since we duplicate and copy the cases for every release and it becomes a tougher task to find the test cases through multiple folders also filtering and linking the cases become a heftier task as the folders increase and cases with same summary.
Approaching to you to get to know that if you can suggest me redirect to the best practice of test case management in jira for the respective release cycles.

Noopur Varshney [AIO Tests]

Hi @Manish Gowda, 

 

AIO Tests comes with folder management for both testcases and execution cycles.

Test cases should be organized in folders based on functionalities and not based on releases. This way you will not need to duplicate cases for each release. Adding cases would also mean you are adding to a single folder which maps to the functionality of your application under test.  

You can use the Release drop-down on test cases to associate the case with a particular release. Also, AIO Tests provides custom fields, which you can use to map additional data pertaining to release with a testcase.

Each release should be maintained as an Execution Cycle or in a folder within the Cycle tab if you have multiple cycles per release.  You can add the same testcase to multiple cycles release over release. The Associations tab of a Case can show you how many times a case has been executed.  

Please feel to reach out to us via help@aiotests.com for further queries/issues.

 

Regards,
Noopur (AIO Tests)