Slides from my talk at CAST 2014, the talk was also recorded and will be available on the AST YouTube channel, https://www.youtube.com/user/TheAstVideos.
More than Just Lines on a Map: Best Practices for U.S Bike Routes
Test Automation - CAST 2014 - Richard Bradshaw
1. Test Automation != Less
Testers || Faster Testing ||
More Time For ET
Richard Bradshaw
2. Richard Bradshaw | @FriendlyTester |
#CAST2014
(Test Automation
!= Less Testers
|| Faster Testing
|| More Time For ET)
{
So what does it equal?
}
3. Richard Bradshaw | @FriendlyTester |
#CAST2014
• Test Automation: The use of
software to perform or support test
activities, e.g. test management,
test design, test execution and
results checking.
ISTQB Glossary
4. Richard Bradshaw | @FriendlyTester |
#CAST2014
Test Automation
Doesn’t Exist
Thank you for listening, enjoy the rest of the conference
Or does it?
5. Richard Bradshaw | @FriendlyTester |
#CAST2014
Test automation is "any use of
hardware or software tools to support
testing".
Personal Communication
Michael Bolton
10. Richard Bradshaw | @FriendlyTester |
#CAST2014
Reduced opportunities for
observation
Stopping using our best tool, our
brain. In this story, two brains.
They reduced Testing / Stop Testing.
11. Richard Bradshaw | @FriendlyTester |
#CAST2014
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.
Testing and Checking Redefined
http://www.satisfice.com/blog/archives/856
James Bach and Michael Bolton
12. Richard Bradshaw | @FriendlyTester |
#CAST2014
Less Testers?
No
Education
20. Richard Bradshaw | @FriendlyTester |
#CAST2014
Exploratory Testing
&
Learn new skills
Build relationships
Get involved earlier
Maintain your automation
Design new automation
More…..
22. Richard Bradshaw | @FriendlyTester |
#CAST2014
Test automation is "any use
of hardware or software tools
to support testing".
Automation in Testing
If we remove the test framework though, we are left with our Automation Architecture.
And so many options jump out….
Data Builder – Create test data for Testing, Demos
Driver + PageObject + Utiles = Use them to collate artifcats for us that we can then test, such as screenshots. SCRUM Idea
A good one Matt Archer once told me, was a heavy data app. Used the automation to write out the data from the tables so he could inspect it.
Data + Driver + PO = Sessions for ET.
Automation is a tool, automation cannot test.
Harness the skills you have acquired in creating checks, to create tools to support all other areas of your testing.
Tools support Testers, they do not replace them.
But Remember….. use your tester skills to decide when and when not to use Automation.