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.
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.
Calling all QA TEST Nerds: How do you document your testing!?
Dear Community, especially those who LOVE testing!
We currently don't have the role of Quality Assurance filled and so - as a project manager, who is not a classic Software guy - I struggle with governing the testing myself.
Our company is still really young and testing isn't quite mature. Lots of testing is going, lots of good software and solutions are being produce, issues in current apps resolved, etc. however NONE of it is documented :'''o(
Devs by nature aren't drawn to documenting and so I am looking for simple ways to help document what's happened.
[Example of my daily struggle: ^in the stride room^ Tech Lead: "Did you test?" Dev: "Yes. Some issues found." Tech lead: "OK"
Any advice? How do you document? What questions are asked? Is it successful with dev teams?
(Yes, I do realise that culture change is needed badly... but a little bit of governance is a nice starting point)
Appreciate any input what so ever :)
