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,559,695
Community Members
 
Community Events
185
Community Groups

Make the tool emphasize requirements, not tests

X-ray is a great tool. However I have a request to make. 

There is a lot of emphasis in the tool's handling of tests. However, when we execute our Verification, we emphasize in what requirements we want to execute regression on.

The use case is this. Given that 600 requirements exist in the project, when 200 of those requirements are deemed critical and regression must be done, then all tests for those 200 requirements must be executed.

As X-ray is implemented today, one have to go find those 200 requirement's tests and add to the plan. Then if requirements change in between or new tests are created, etc, one has to manually keep things in sync.

We have to resort to building these programs that allow this to happen and it is starting to get out of hand.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events