Four Stages of Automated Testing by Bradley Temple

4 Stages of Test
Automation
Welcome to your ﬁrst day at fake-amazon.com

Expectations
• We will move quickly, as there is a lot of content and 3
and a half hours will go much faster than we think it will

• The virtual machine thing was the best I could do without
having time to work with anyone ahead of time, as setting
up a working dev environment is non-trivial, if you
couldn’t get it going, pair up with someone who did

• If you have something in particular you are hoping to get
out of the class, put it up on the class backlog and I will
try and get to it.

Expectations
• You’ll get some time to try each stage on your own or in a
pair before we go over it as a class. Ideally you’d get a
couple hours to experiment with each stage, but we’re
running on a compressed timeframe.

• You won’t be an expert when you leave today, but you’ll
hopefully have a better idea of what the mistakes you’ll
make along the way look like so you can move past them
easier.

Agenda
• 8-8:15 - Working Agreements, Class Backlog

• 8:15-8:45 -Automation Crash Course (New Hire Training)

• 8:45 - 9:15 - Stage 1 - A basic Test

• 9:15 - 9:30 Class Walkthrough of Stage 1

• 9:30 - 10 Stage 2 - Cucumber

• 10-10:15 Class Walkthrough of Stage 2

• 10:15-10:45 Stage 3 - Gherkin as a Speciﬁcation

• 10:45 - 11 Class Walkthrough of Stage 3

• 11-11:15 Class Walkthrough of Stage 4

• 11:15-11:30 - Questions and Answers

<html>
<body>
<div>
<p>
<strong>Hello</strong>, what’s up?
</p>
</div>
<div>
<a href=“http://google.com”
id=“google-it”
class=“btn btn-primary">
>Google It</a>
</div>
</body>
</html>

<a href=“http://google.com”
id=“google-it”
class=“btn btn-primary”>
>Google It</a>

Open your Terminal Application
Under System Tools
And type these commands
cd ruby-crash-course
bin/start

DEMO: Messing around
with automation in the
console

So you’re the new hires? Great. Fantastic.
We’re trying to ship our new feature. Hold
onto your hats, we’re gonna ship everything
for FREE on orders worth more than $35.

We need some tests around it but manually
adding stuﬀ to the cart is taking too long.

I heard you know how to automate
websites, so if you can make that happen,
it’d be great.

Stage 1 - Testing with
Scripts

git clone https://github.com/DVG/fake-amazon.git
Open your Terminal Application
Under System Tools
And type these commands
cd fake-amazon
bin/bootstrap

How to do it
• Your script is in the script directory.

• You can run it by executing bin/run-test

• If things stop working, run bin/bootstrap again

• I’ll be walking around, if you need help, ask

Things we should do in our
script
• Log In (student@example.com / supersecret)

• Add a cheap item to the cart

• Visit the checkout page

• Add an expensive item to the cart

• Navigate to the checkout page

• Complete checkout

Problems with this
approach
• Relies on ‘known data’

• Can’t be re-run (application state is changed as a result of
the test run)

• Doesn’t actually test anything

• Lots of repetition

• Tied to UI Details

• Not clear what the feature being tested is

So I went to a conference last week…
Hey that script you wrote is great, just
great. But everyone was talking about this
cucumber thing, have you heard of it?

You can just write your tests in english and
you don’t need any of that code stuﬀ, since
no one knows what that does anyway.

How about we redo it with the Cucumber?

So I was chatting with the devs…
Everyone loves what you’re doing with the
testing stuﬀ

Except the devs, of course , they hate it.

They’re trying to use the speciﬁcation for
the mobile app, but it super doesn’t work.
Can we make it just, like, general?

Stage 3 - Speciﬁcation By
Example

Hey, that spec is great. We’re gonna use it
on the mobile app too.
So about those breaking tests

But tests are still breaking when some stuﬀ
changes. The dev said you can do some
kinda object doohickey to ﬁx it. Maybe pair
with them on it?
So about those breaking tests

Object Oriented Programming
(A hasty primer)
• Objects

• Receive Messages and produce Behavior

• click_link is a message that invokes the behavior of clicking an <a>
tag

• Is a model of a thing or idea in the real world

• Hide moving parts behind a particular interface (Encapsulation)

• Allow diﬀerent objects to receive the same message but respond
diﬀerently (Polymorphism)

• Can gain behavior from a parent (Inheritance)

(A hasty primer)
• Classes

• Define a thing

• Person is a Class

• Instances

• A specific thing based on the definition (proper noun)

• Bradley is an instance of Person

(A hasty primer)
class Person
attr_reader :name, 
:bmi, 
:blood_pressure, 
:pulse, 
:last_slept_at, 
:support_network, 
:hunger_level, 
:personal_sense_of_satisfaction, 
:insecurities
def how_are_you_feeling?; end
end

(A hasty primer)
person = Person.new(“Bradley”, *other_attributes) 
person.how_are_you_feeling?
# => “Fine”

(A hasty primer)
class Tester < Person
def how_are_you_feeling?
process_last_interaction_with_a_developer()
super()
end
end

(A hasty primer)
person = Tester.new(“Bradley”, *other_attributes) 
person.how_are_you_feeling?
# => “Irritated”

Page Object
• Up till now we’ve been sending message directly to an
object controlling the browser, so all of our test code is
written in terms of low-level detail of browser interaction

• People do not think about whether something is a button
or a link, people think about tasks that they want to
complete on a page.

• A page object provides a way to hide away the details of
browser interaction behind a more intuitive task-based
message interface

Stage 4 - Page Objects
(class exercise)

Four Stages of Automated Testing by Bradley Temple

Four Stages of Automated Testing by Bradley Temple

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Four Stages of Automated Testing by Bradley Temple

Similar to Four Stages of Automated Testing by Bradley Temple (20)

More from QA or the Highway

More from QA or the Highway (20)

Recently uploaded

Recently uploaded (20)

Four Stages of Automated Testing by Bradley Temple