Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

[] Can we lock down executed tests?

When a test specification has been created in Zephyr, and then subsiquently executed. Could we lock down the executed test record so that any future adjustments to the test steps will not update historic executions of the tests.

This will help us in keeping an accurate record of the actual tests performed. The same feature may have been tweeked slightly in a subsequent version of software (for example) and so the test needs to be re-run in a second test cycle but with a few minor tweeks to the test scripts. At present if I update any test scripts, then they are updated for all executions that have been performed and this does not givce an accurate record of the tests performed at that time.


1 answer

Probably it's been already resolved, but for cases like this the best approach would be: to contact the app vendor directly :)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events