I have created a user story and idea is to link with Test Sets and then Tests and Test Execution.
When we run via scrum, then it good to have to walkthrough just via User story.
I am not able to find how to create the test execution set from user story or test execution set link and visible at user story level.
Any suggestions ?
Well. The reason why you see that because the filter in the "Test Coverage" part of a user story has "latest execution" and "All environments" selected by default. In agile the focus is on the user stories(requirements). "Is the product behaving as it supposed to?" that is the question. Xray complements it by allowing us to link the test cases to make sure that the requirement works or not. So linking all wanted test cases to a user story(requirement) and also executing and passing all those test cases( in a particular version) means that the requirement has been implemented properly. So even if you are executing the same test case as part of another user story in the same version of the product the status will reflect in the old user story because the previous requirement is also being validated automatically. This removed the documentation overhead to track what test cases a tester executed for different user stories for the same version of the product.
Coming back to your question, to see the added test cases in "TODO", all you have to do is to select the version under test in the "TEST COVERAGE" section of the user story. You have to add the version that is under test in jira to be able to do that. Also you will be able to see all the execution done for the test case as part of testing the user story, knowingly of unknowingly under test runs.
You can link a requirement (Story) with a Test Set (instead of individual Tests) using the "tested by" link type.
This way the requirement will be tested by all the Tests that belong to the Test Set.
Additionally you can create Sub Test Executions as the requirement sub task and then put the Tests from the Test Set into to this Sub Test Execution.
And this way you can track down the Test Executions (Sub) associated with the requirement in the Agile boards.
Please check our documentation about Agile Enhancements here: https://confluence.xpand-it.com/display/public/XRAY/Agile+Enhancements.
Thanks once again but this lead me more confusion :(
I have user story linked with test set now and that test set linked with Test plan having test execution set with say Pass, fail and pass status for 3 test cases.
Now I have another user story and want to re-run the same above 3 test case. I have linked the test set with user story now then I could see all three test cases are now populated with Pass, fail and Pass status which I think is incorrect.
I am expecting default status should be TODO so when I can create test execution out of test plan then the status should reflect accordingly.
Am i making sense here ?
I have the same problem, is there any way to work around this?
If you have the same TestCase linked to different uset stories, it will be nice to have a different status for them, somehow to make a correlation with the test execution linked to that US.
There might be some confusion about this since, in Xray, the User Stories are linked with Tests and not Test Executions.
The idea is that in Xray, a requirement (User Story, Feature, etc.) is tested by a Test case (or group of tests: Test Set).
Suppose it is necessary to have a specific Test Execution to test a given requirement. In that case, it could be an option to create a specific Test for that particular requirement so that a specific Test Execution is related to the requirement through the specific Test case.
This is the way Xray was designed, and it is supposed to be used.
However, if this solution does not work for you, it is best to contact Xray Support (http://Xraysupport.getXray.app) to share your configuration so that the support team can investigate an alternative that suits your needs.
Rogerio Paiva [Xray Support Team]
Yes, in the User Story you will see the result of all the Test Execution status, and you may also analyze it from the scope of a specific release.
You can know what is the status of User Story A based on the tests of release 1.0, if you use the scope for release 1.0. And the status of the User Story A based on the tests for release 1.1, if you can change the scope to release 1.1.
Rogerio Paiva [Xray Support Team]
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...