We have the situation that we have a running testexection. After this testexecution we changed the testcase (e.g. testdata). This Change also changed the existing testexecution. That means that the testexection is not maintained and does not reflect the situation while running this test. How can this be avoid?
As per the testing methodology or process a test case data once written and added to the test case cycle,once executed maintains its relation to the test data present at the time of execution.Changing the test data means it doesn't maintain the relation with previous execution as the test steps related to previous executions have changed.Therefore editing a test case doesn't preserve the old execution details.This is by design.If you have to change the test case we suggest you to clone the test case and add to a new test phase cycle.
this sounds not good . That means that the results of the testexections can be manipulated after running and there is no possibility to maintain the Situation for this execution. For our planned environment it is not realy feasible that the testcase should be cloned for each change as this is a manuel process.
Do you plan any change on this issue?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs