Replies to Avoid adding linked test cases to Execution cycle

Hi Vikrant,

In your current setup you can try moving your common reusable cases to a separate folder and not include it during creation of cycles.

Going forward you can try the following recommendation to utilize folders in a better way:

1. Create your cases folder structure by features/functional areas
2. Keep common cases like login and common navigation etc in a separate folders
3. While creating cycles pull cases from folders of features only so that reusable common cases are not duplicated.

Thanks and Regards,

Vishal Srivastava

Hi Vishal,

Thank you for suggestion, if i use the below suggestion than the responsibility to update the test case is vague as it does not fall into any teams responsibility area.

That is why i was trying to find another way to resolve this.

Regards,

Vikrant

Hi Vikrant,

May be you can try using case owner or multi user selector type custom field or both to establish the responsibility for maintaining cases. Team wise tags can also be created and linked with cases to further ease the process.

Hope that helps!

Thanks and Regards,

Vishal Srivastava