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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,015
Community Members
 
Community Events
176
Community Groups

What is the best way to deal with automated tests in Scrum

Background - we are a scrum team using Jira Xray for our manual and automated tests. Our automated tests must go through code review via our development team.

Our current process stipulates that when a test is created or amended there must be a linked Jira ticket i.e. Create new automated test for x/Amend automated test x

I am trying to move away from so many tickets. As the QA team identify a need to amend a automated test, we want to make the amendments and submit a pull request on the existing Jira test. I am told that working in this way does not provide a reason for the code changes and therefore goes against our standard for code so cannot pass code review. I am told that we must create a linked Jira ticket explaining the change.

Is anyone able to advise how we can satisfy the standard for code and provide that reason without the need to create the additional tickets?

0 comments

Comment

Log in or Sign up to comment