We are looking for a test management tool for Jira. Our QA use exploratory testing, so they create test cases with a few general steps and then they update those steps while executing the test. Basically, they want to edit (update/add/delete) the steps of the test run created from the test, without changing the original test.
It seems like it's not possible with Zephyr or Xray.
Do you know of other tools that provide this kind of functionality?
If you are looking for a test management plugin for JIRA, it may worth to have a look at SynapseRT. It can organize your test cases as a TREE (folder) strucure. It also provides end to end traceability between requirement, test case and test result (defect). It also helps user build requirement hierarchy and test case coverage.
If you are interested in it, you can book a demo here.
From my QA experience, the use case you mentioned above is not a valid one for QA testing, at least it is not a best pratice for test process.
If you are going to test different scenarios, you should start from different test cases. Instead of using the same test case, but later change the orginal test scenarios (described in test case) from test execution (update/add/delete), normally test execution is a snapshot of your orginal test case and not allowed to edit steps there.
In SynapseRT, you can clone a test case with steps, and then do minor modifications to make it suiable for new test scenario.
And then create 'Add Hoc Test Run' from each test case to record your exploratory testing results.
You also can add 'Comments' for each of your test execution (started from the same test case) to record the addtional execution information.
In the traditional approach, each test has steps created in advance and describing exactly how to execute the test. The test runs inherit those steps and the test is performed exactly the same way, every time it is executed.
In exploratory testing, one test can be executed differently every time it is executed. Our QA write tests with very general steps or without steps at all. When they execute the test, they write down the steps they performed in order to test the objective of the test. The original test is not updated with those steps - they are part of the specific test run.
It's ok if you don't agree with this technique - there are a lot of different methodologies out there, you don't have to embrace them all :)
From what I see SynapseRT doesn't offer the functionality we are looking for.
Thanks for your reply!
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events