Which test management tool has test scenario feature?

[mail2dwarak]

User story - Test Scenario - Testcases. This is how we have derived test design process. But it's hard to find tools that support the test Scenario feature.

We are exploring Xray and qmetry. 

Need suggestions please.

[Sahashraanshu · Accepted solution]

Hello @mail2dwarak,

I recommend QMetry for Jira as a tool based on your testing process.

The Test design process that you have mentioned: User story - Test Scenario - Testcases, was indeed followed by QMetry for Jira in the earlier versions. As per your process, it seems like you would want to use the Test Scenario for grouping logical Test Cases so that you do not miss the scope and just link the Test Scenario to the User Story instead of directly linking the Test Cases. However, users at times got confused because grouping Test Cases in Folders in the Test Case module and grouping them in Test Scenarios served the same purpose and made the process more complex by including an additional issue type in the case of Test Scenario.

In conclusion, the current version of QMetry for Jira implements the Folder Structure that allows the tester to group their Test Cases based on components, modules, functional area, sprint, release, etc. So the Test planning and traceability in QMetry for Jira looks like:  User story >> ( Folders - for grouping Test Cases) >> Testcases >> Test Cycle. While associating Test Cases to a Story or Test Cycle, the tester can search and filter them on the basis of the folders they are located in and bulk-link them. Similarly, the folder structure is available at the Test Cycle and the Test Plan level which helps in keeping the user experience consistent throughout. Additionally, while exporting the Test Cases, the folder structure is retained in the exported excel sheet. 

I would recommend you to use Folders instead of Test Scenario as that provides more flexibility and easier workflow.

Regards,

Maverick (Sahashraanshu)

[mail2dwarak]

Thanks Sahashraanshu. This was very helpful. Got an insight of how to implement.

[Niharika [AIO Tests]]

Hello @mail2dwarak,

If you are still looking for a solution, AIO Tests for Jira supports scenarios. 

It allows you to

• design your cases as per functionality by putting them in folders.

• If there is a particular scenario, then AIO Tests supports grouping cases across functionality by Sets. 

• You can even tag cases to define a particular group of cases.

If you would like a demo, then please contact our support.

[Rogério Paiva - Xray Xporter]

Hi @mail2dwarak 

You can use Xray to implement Test Scenarios.

In Xray we don't have the term, but it can be easily implemented using Test Sets and assign the testing of a Story to a Test Set, instead of a single Test case, making the Test Set, your test scenario.

Please contact the Xray Support (http://xraysupport.xpand-it.com) so we can schedule a product demo with you.

Kind regards,
Rogério Paiva [Xray Support Team]

[Radoslaw Cichocki {Deviniti}]

Hi @mail2dwarak ,

Which hosting are you on?

If it's Server or DC, then you may want to check out TestFLO - Test Management for Jira.
We have a concept called Test Case Template, which most likely reflects your Test Scenario. Templates are non-executable, contain test steps, and are used for procuding executable Test Cases stored within Test Plans. The templates can be organized into a re-usable test repository (tree of folders).

So, the flow is:

1. Cover requirements with Test Cases Templates and organize them in the test repo
2. Create Test Plans out of the folders (or manually, by indicating the templates that should be used to create Test Plans)
3. Execute the Test Plans - you can do this in iterations. Then you can narrow down the set of Test Cases that you want to re-run within the test plan iteration by iteration.

If you're on Jira Cloud, you may want to chek out Requirements & Test Management for Jira.
My colleague will add a few sentences regarding this product in a while.

Disclaimer: I represent Deviniti, the maker of both of these tools.

Regards,
Radek Cichocki