You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have requirements tested by tests
I have several coverage statuses according to different versions (Version1 OK, Version 2 OK)
If I have Version 2 OK for my requirement and if I update a test, I though that my coverage would be reset.
If I go to my test execution for Version 2 and If I do reset, my coverage is set to "not run". Is it possible to automatically reset the test executions after a test details update ?
Hi @Tristan FAURE ,
the rules for calculating the coverage status are describe here.
There's also a free course on Xray Academy covering this topic.
In brief words, the status of a requirement for some version depends on the latest results that you obtained for the related tests, on that version (i.e., on test executions assigned to that version).
Let's say that you have this scenario:
if you now change the specfiication Test X, user story A will still be OK because it is based on the results that you recorded.
Note: eventually you could use the workflow status, the one that is part of the Jira issue, to signal that. There's an example on the docs using ScriptRunner (for Jira server/dc) but for the opposite case (i.e. when changing a requirement, change the workflow status of the related Tests). If you're curious about it, please have a look at it.