Beyond automation

-Be part of an efficient team

About me

• 1.5 years QA rookie• Carsales.com.au

Sean

1 per week

2-5 x per day

BUGs vs Releases

Releases

Bugs

Challenges• Bugs• Releases

• Communication• Environment

How the clock turns

Automate

VisibilityTest Tooling

Efficiency

Team

Test efficiently

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

Test efficiently

Automate efficiently

Automate efficiently

More automation Better Coverage

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

More visibility improves efficiency

• Why visibility is Crucial?• Awareness

• Reduce reliability/dependency

• Show the progress

Visibility - Aggregate Test result

Visibility – How

• Simple and concise – Show minimum – result/numbers

• Smart Alerts

• Accessible, e.g. TV

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

Tooling – 200oker

https://github.com/carsales/200oker

Tooling – Chrome plug-in

Tooling – Device lab

Tooling – What if I don’t have time

• Inefficiencies are expensive

• Start with 1%

• Show your team your progress

Now• Easier release

• Lower bug rates

• Team bonding better

• Better perception

• Fun stuff

Fun stuff - Hackathon

Test on The ToiletPerfect customer experience starts with a P.

Volunteer day

And some more…

• QA No limitation

• Never stop learning/adapting

• Problems solution

• More sharing and communication with QA community

Questions?

thank you