Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Xray requirements coverage tracking for legacy features

Xtian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2023

Hello,

I would like to get some advice or tips how to achieve following scenario within Jira Xray.

Assume I have implemented a feature A via a story A for the product version 1.0.0
During the implementation of feature A there were five tests created and linked to this  Story A. Within the release testplan of version 1.0.0 all five tests were executed and passed. Xray does show 100% coverage.

So far so good.

Now we are working on new product version 1.2.0. We will implement another feature B in Story B. Feature B is been covered by eight tests.

For the release testplan I need to run the eight tests of the newly implemented feature and one single test for the old feature A. The other three tests linked to Story A are not needed within the testplan of version 1.2.0 (We simply just need to ensure that feature A is still working as before - and this can be achieved by running one testcase)

I want to see 100% coverage on feature B (when all eight tests are passed) and 100% coverage on feature A (when this specific single test is passed)

How can I achieve this within Xray? Is there any best practise how to consider features (newly developed in current product release and needed to be extensively tested) and "legacy" features already implemented in previous product version (and now only need some few regression tests)

Thanks a lot

1 answer

0 votes
Stefan Salzl
Community Champion
April 6, 2023

Hi @Xtian 

in general I got your point. Talking as a former QA lead there are some questions coming to my mind:

  • As there was (in your case) only 1 test case of feature A executed would could you say it has a 100% coverage (in this iteration/version)? The point is it had a 100% coverage in version 1.2.0 when everything was tested. But as you are "just" running the regression of feature a in 1.2.0 would the tool telling the truth if it says 100% coverage when only 1 of its test cases were executed?
  • Isn´t it more a question of your test strategy? Like let´s say (and I really love your concept of having a test plan for a version) have a 100% coverage which doesn´t mean that each feature itself has 100% test coverage but all the tests that were meant to fullfill my test plan/test strategy. (We had that strategy in the past where prio1 test cases were added to the "regression test set" and executed with each version - the testplan itself had a 100% coverage but we decided that only the most important tests of legacy features were part of the test plan).

Best
Stefan

Stefan Salzl
Community Champion
April 28, 2023

Hi @Xtian 

any update/feedback?

Best
Stefan

Suggest an answer

Log in or Sign up to answer