Upload
stephen-janaway
View
59
Download
2
Tags:
Embed Size (px)
Citation preview
Who am I?Stephen Janaway
• Testing for the last 14 years.• Mobile phones, mobile networks, mobile
applications, web and web services.• Ericsson, Motorola, Nokia. • Test Coach, Trainer and Strategist at the NET-A-
PORTER GROUP.
www.stephenjanaway.co.uk @stephenjanaway
What Does It Mean?
Trying the software to see if it works...
What does “try” mean?
How do you know what “works” means?
It’s actually...
Questioning and investigating the software…
...to infer from it’s observed behaviour how it will behave in the field, and to identify important problems in the product…
...so that stakeholders can make an informed decision on it’s suitability for release.
Checking vs. Testing
Testing is “the process of evaluating a product by learning about it through experimentation, which includes to some degree: questioning, study, modeling, observation and inference.”
Checking is “the process of making evaluations by applying algorithmic decision rules to specific observations of a product.”
So Can Automation Replace Testing?
➔ Testing is more than checking.➔ Automation scripts only do what they are
instructed to do.
You can only check what you know and expect. Customers don’t always do what you expect.
We Can’t Automate
Thought patternsExploratory testing
UsabilityUser reactions
CompatibilityClaims testingPerformance
Look and feelUnknown behaviours
Accessibility
So Who Does the Automation?
➔ Developers➔ Testers➔ Developers in Test (if you have to)➔ Different people focus at different levels.
Not separate ‘automation’ teams
My Ideal Setup
➔ 6 developers, 1 tester in a cross functional team.
➔ Automation primarily a ‘development’ activity.
➔ A thin layer of UI tests.➔ A thick layer of unit tests.➔ Quality owned by the team.
Questions?
“Hang on Steve - you haven’t talked about TDD, BDD, Selenium, Appium,....”
Stephen [email protected]