To test this feature, visit your live site.

Proper way to use cases | sets | cycles?

Hello,

We've been using AIO in a specific manner, but we've encountered a small issue and wanted to check if we're correctly utilizing test cases, sets, and cycles.

Our process is as follows:

We start by creating test cases, organizing them into folders based on product areas.
These test cases are then added to test sets corresponding to their related user stories. We maintain two types of test sets:
- A Regression Pack set
- User story-specific sets
When executing a test cycle, we ensure it includes both the regression pack and multiple user story-oriented test cases, to represent all testing activity done for a release.

The issue arises when test cases from a user story set are also included in the regression pack cycle. In this case, the test cycle appears to reflect results for both the user story and regression pack, as the test case is linked to both.

Is this the correct way to be managing cases, sets, and cycles in AIO? Or should we be structuring them differently to avoid this overlap?

Thanks in advance for your guidance!

5 answers0 replies

5 Comments

Niharika Varshney

Feb 07

Hello,

The management of cases and sets is perfect. When the same case belongs to multiple sets, and if these sets are used to create a single cycle, the cases are added only once. So, this should not cause duplicates.

Are the sets being used to create different cycles from the sets (one from regression set and one from story set)? Or are the cases being used as linked cases? Can you please elaborate the scenario, so that we can better understand the issue and suggest.

Regards, Niharika

Niharika Varshney

Feb 11

Replying to

Hello Cameron,

Today, AIO Tests doesn't store a mapping between what sets were used to create a cycle. And hence the display shows all sets where the cases belong. It would also be a challenge for AIO Tests to make a decision on which sets to show or not to show. Would grouping by folder/component in reports be a better view in your scenario?

Regards,

Niharika

cameron.fairburn

Feb 11

Replying to

Hi Niharika,

So we would like to be able to display the sets in this manner because it shows the test scope of the test cycle. As the folders display the product area instead, it is less informative.

By displaying the sets, we can understand the work that went into a cycle, something like:

Regression Set
PR-139 Add a table UI
PR-140 Add a table API
PR-001 Bug fix

This gives full visibility at a high level that everything going into a release was tested. I am not sure how we can achieve this without removing things from old sets potentially.

Cheers,

Cameron

Niharika Varshney

Feb 12

Replying to

Hello Cameron,

Thanks for adding more context. Can you please let us know which report are you using? Or are you using the group by on cycle details page?

Regards, Niharika