[Structure+Testy] Make it possible to have a type of parent child relation inside an issue
Use Case 1:
As a tester I would like to use a unique test case and run it several times and after every run I would like to add my test data/environment to it. (E.g. Result and what format, browser, platform, DB that was used during test run...)
Use Case 2:
As a Test Manager I would like to be able to create a dashboard report or filter based on specific data and the outcome of the result with that test data/environment.
Current solution with testy today (https://marketplace.atlassian.com/plugins/com.almworks.testy)
has some good features but you still lack the method to add specific test data/environment to a test run without making a clone of the original test case and without having to plan and create a complex setup based on strict test with env/data defined on test and many test run columns.
Test results presented on a run in structure with Testy cannot be collected and presented in a report outside use of the structure.
Collecting requirements – please see the comment.
Thanks for your question. It could actually be a separate idea!
Current version of Structure.Testy cannot provide this functionality out of the box, however, it could be automated through REST API and some additional "agent" program, which detects test run status and updates issue status.
We can plan a feature in Testy that would automate issue status change, however there are certain questions that needs answers --- for example, if issue status is updated to "Passed" because the latest test run is Passed, what happens if a new test run is created? Are all "Passed" issues become "Not Passed" again? Do only some of the issues change?
I've also added a feature request for associating a date or a version number with a test run, so it's possible to tell which one is the latest - https://jira.almworks.com/browse/STY-47
Helen Oakley commented
Is it possible to also have JIRA status updated based on the latest test run (map to and update JIRA status)? If yes, how would you define "the latest test run"?
Robert, thanks for the explanation. Got it now.
We intend to add a free-form text field, editable in/around test run column, so the user can type any comments regarding why the status is marked passed/failed.
We also consider adding a panel to the issue view that would show the status of the issue for the test runs that it was in.
As for more complex scheme of configurable fields per test run - that is a bit out of scope. Structure.Testy was supposed to be a lightweight solution, easily usable without much configuration, and not a full test management suite. Did you try other JIRA-based testing tools like Zephyr (I believe there are others too). As much as I would like you to use our product, if what you need is actually something else, then it's better to use something else! Actually, if those plugins didn't work for you, it would be interesting to get your feedback, why.
PS. Oh, actually - we have a thought to associate a Test Run (as a column) with an issue. So then - if the user defines "Test Run" issue type, and associates test runs with those issues, it will be possible to have JIRA's custom fields functionality for the test runs. It will take some glue to make the data searchable through JQL, but I think it could be done.
Robert Olsson commented
Hi Igor, thanks for your response. Yes I will explain.
So Im thinking that it should be possible to enable a separate view inside the jira issue that keep tracks of every test run you execute on this test case (jira issue) and as well the information/test data you want to add for every run (configurable fields). One key factor here is that all information must be searchable and connected with the main issue (the test case) for creating test reports. So when saying parent i refer to the jira issue and child would be every test run.
Another way is to enable some method to add test data/information in the testy column together when adding passed/failed to the test. Same key factor here all information added (e.g. test result/test data) must be searchable and connected with test case (jira issue) to enable the option to create test reports.
Thank you very much for your feedback! It makes sense and falls in line with our thoughts about future Testy features.
I'm a bit baffled by the idea title though - could you please explain what did you mean by "type of parent-child relation inside an issue" and how it connects with the necessity to have environment parameters and reports?