Carsales has been through a huge leap on efficiency in the past few years. We moved to micro service architecture, we went from doing deployments 1-2 times a week to multiple times a day. We migrated from gigantic legacy system and put our system in the cloud at the same time improved quality. How did QA team in Carsales manage to ensure the quality of every release? Also, how did we not slow things down but helped to make delivery smoother and provide the team with more confidence? I will talk about the improvements we did beyond automation, to help us keep up with the pace.

2. Beyond automation
-Be part of an efficient team

3. About me
• 1.5 years QA rookie
• Carsales.com.au

5. 1 per week
2-5 x per day
BUGs vs Releases
Releases
Bugs

6. Challenges
• Bugs
• Releases
• Communication
• Environment

7. How the clock turns

8. Automate VisibilityTest Tooling
Efficiency
Team

9. Test efficiently
• Utilise your team
• Commence testing early
• Test environment
• Very little big end to end
• Automation for regression + Exploratory

10. Test efficiently

11. Automate efficiently

12. Automate efficiently
More automation Better Coverage

13. Automate efficiently - How
• Shift more test to api/code level
• Separate your suite
– Regression suite:
• Light weight
• Fast stable
– Big suite
• Runs over night for sanity check

14. More visibility improves efficiency
• Why visibility is Crucial?
• Awareness
• Reduce reliability/dependency
• Show the progress

15. Visibility - Aggregate Test result

16. Visibility – How
• Simple and concise
– Show minimum – result/numbers
• Smart Alerts
• Accessible, e.g. TV

17. Tooling – QA Idea generation
• Guideline
– 80% tactical 20% strategic
• A good tool should be:
– Easy to install/setup
– Easy to use
• Share your tools
• Developers contribute

18. Tooling – 200oker
https://github.com/carsales/200oker

19. Tooling – Chrome plug-in

20. Tooling – Device lab

21. Tooling – What if I don’t have time
• Inefficiencies are expensive
• Start with 1%
• Show your team your progress

22. Now
• Easier release
• Lower bug rates
• Team bonding better
• Better perception
• Fun stuff

23. Fun stuff - Hackathon

24. Test on The Toilet
Perfect customer experience starts with a P.

25. Volunteer day

26. And some more…
• QA No limitation
• Never stop learning/adapting
• Problems solution
• More sharing and communication with QA
community

27. Questions?

28. thank you