►
From YouTube: Why tests should be written with Action Groups only
Description
1. Simplifies maintainability
2. Reduce duplication
3. Action groups are tested in lots of different scenarios which makes them more stable
- 🤣 Good example: LoginAsAdminActionGroup.xml
4. Enhances extensibility
B
Okay,
guys
so
I
think
we
can
part
I,
don't
know
what
Ryan
of
you,
but
internally
in
our
company,
we
have
core
quality
engineering
medians.
We
do
them
by
quickly.
We
do
them
by
weekly.
Those
meetings
will
try
to
share
useful
information
for
everyone,
how
to
write
tasks,
how
to
build
testing
strategy.
Basically,
we
are
nerds
here
we're
talking
about
how
to
test
Magento
and
how
to
how
to
not
a
developers.
Happy
today
is
firstly
in
where
we
share
our
knowledge
with
community
and
I
hope.
B
B
He
is
explaining
in
this
quick
guides
our
mighty
F
works
in
basics
and
I
shared
in
Twitter
and
in
I'm,
acting
up
slack
channel
this
playlist
on
my
channel
communication
and
YouTube
channel.
So
if
you
will
not
get
some
points
today,
please
go
ahead
and
you've
left.
You
have
quick
guide
about
actual
groups,
so
this
is
basics.
I
will
not
talk
about
basics.
I
will
talk
more
in
high
level
why
it
is
important
to
you.
B
B
There
is
a
page
where
I
listed
all
of
the
action
groups
with
descriptions.
We
just
started
working
on
this
page,
but
it
may
be
not
very
useful
today,
but
we
are
kind
of
this.
It
will
be
better
and
better
day
by
day,
so
please
go
there
and
find
it.
I'd
also
included
a
link
in
the
last
slide
with
useful
links,
but
you
probably
will
ask
a
question
of
this
question:
why?
Why
do
I
for
section
groups?
Why
do
I
force
everyone
to
write
tests
with
action
groups?
So
I
can
explain
you
with
this
bullet
points.
B
So
if
you
use
already
exist
an
action
group
you
and
be
saving
your
time
and
right
in
this
test
and
maintaining
those
action
groups
is
much
easier
because
if,
if
you
have
ten
falen
tasks,
because
your
product
cannot
be
added
to
shopping
cart,
let's
say
it's
going
to
be
much
easier
to
update
one
single
action
group
which
do
it
and
all
other
tasks
will
be
fixed
automatically.
You
don't
need
to
go
to
each
of
these
tasks
and
fix
the
other.
B
B
Action
groups
are
tested
in
lots
of
different
scenarios,
which
makes
them
more
stable,
but
this
I
mean
and
I
have
an
example
here,
login
as
admin
action
group.
That's
our
best
actual
group.
We
have
my
child
for
an
FDF
tasks
by
this
I
mean
that
this
action
group
is
used
almost
in
every
single
task.
We
have
in
Magento,
and
we
did
everything
to
make
this
table
this
action
group
as
stable
as
possible.
So
I
never
saw
that.
We
have
either
on
this
login
as
admin
tab
because
we
tested
it
in
many
many
many
other
tests.
B
If
we
will
do
with
other
steps
with
other
actions
the
same,
they
also
will
be
tested
in
different
areas
in
different
places,
and
the
different
people
will
make
this
action
group
much
more
stable
by
adding
their
proper
weights.
Writing
proper
selectors
data,
whatever
needed
made
it
stable,
and
the
last
point
which
we
will
talk
more
about
later,
is
using
action.
Groups
enhances
extensibility
of
our
costs.
B
So
let's
talk
about
it.
Warm
during
have
an
example.
I
will
talk
on
some
magenta
scenarios
and
I
will
talk
today
about
customer
looking
form
and
how
we
can
write
a
test
volume,
as
customer
and
I
will
have
three
examples
of
today.
First
one
is
vanilla,
magenta
with
magenta
fields.
Second,
will
be
my
gentle
last
cup
chat,
enabled
with
capture
extension
in
third
example,
will
be
my
gentle
plus
capture
extension
and
plus
two
FA
expansion
when
we
have
multiple
expansions
tables
on
my
checklist.
B
So
that's
what
we're
gonna
talk
him,
that's
what
we're
gonna
try
to
cover
with
Emma
TF
test.
So,
as
many
of
you
know,
that's
how
our
tests
look
like
that's
excellent.
Only
with
declared
actions,
those
actions
are
very
readable,
I
believe
that
key
in
their
sections.
This
is
our
unique
identifier,
so
it
is
very
important
to
write
them
unique
and
scope
of
caste,
and
you
will
understand
why
later
so,
what
this
test
will
do.
It
will
first
feel
email
feel
then
feel
password.
B
What
will
happen
if
we
will
have
capture
module,
enable
definitely
all
of
you
under
and
it
but
I'll
show
you
the
test
will
fail
because
magenta
will
say:
hey.
You
have
one
more
required
how
to
solve
this
problem
to
solve
this
problem
here
at
the
top
we
have
same
a
gentle
past,
which
is
located
in
magenta
with
this
sorry
guys,
which
is
located
in
magenta
customer
module
and
does
same
steps
as
I
showed
you
before
and
down
here.
You
can
see
time
task,
name,
custom,
elegant
task
and
I
split
it
by
this
line.
B
It
means
that
this
piece
of
task
can
be
located
in
any
other
module
or
in
any
extension.
So
if
you
will
declare
a
test
with
the
same
name
as
in
as
we
have
a
gentle
task,
they
will
behave
very
very
interesting.
Let
me
show
you
how
so
when
the
when
we
will
run
customer
working
task
first
of
all,
it
will
fulfill
the
male,
then
feel-feel
password
the
magic
will
happen.
Do
you
feel
filled
from
your
expansion
or
your
own
module
will
be
merged
in
main
Magento
chasm.
B
B
Make
it
will
happen,
it
will
go
capture,
field,
click,
Sign,
In
button
and
obviously
test
for
possum.
Oh,
that's
how
our
merging
and
how
you
can
extend
your
task
works
with
Emmet
I
think
happens
if
you
have
qfa
extension
installed,
so
we
have
agenda
fields.
We
have
capture
extension.
If
you
do
FA
extension
on
magenta
to
sidebar,
so
the
same
magenta
to
test
can
be
extended
by
caption
test
extension,
as
I
shown
you
before
the
same
thing
can
be
written
from
2fa
extension.
B
They
a
good
part
about
it
that
both
of
these
extensions
they
know
only
about
my
gender.
They
know
only
about
my
channel,
you
tasks
and
this,
but
when
they
expand
this
task,
these
two
expansions-
you
don't
know
about
each
other
and
they
are
not
depending
on
each
other.
So
this
is
good,
but
the
main
question
why
I'm
still
not
talking
about
actual
groups.
B
And
I
want
to
ask
a
question:
what
will
happen
if
each
of
this
X
function
has
their
own
as
their
own
in
test?
How
can
they
be
extended
and
how
can
they
work
without
knowing
about
each
other?
So,
coming
back
to
our
form,
what
we
can
do.
We
can
have
two
FA
test,
caption
test.
They
don't
know
about
each
other
caption
test
expansion
can
expand
to
f8
and
expansion
can
extend
caption
test
but
at
the
same
point
of
time,
will
break
the
idea
that
this
has
do
not
know
about
each
other.
B
B
And
this
magenta
to
task
is
reeling
with
my
Chandra
to
action
groups,
then
purify
expansion
and
expand
this
action
group
and
do
not
touch
tasks
and
because
my
chapter
two
it
has
this
using
this
action
group
and
this
action
group
is
extended
by
this
extension
of
anytime
I,
said
Expo,
and
because
this
traffic
extension
extended,
which
entered
Direction
group
magenta
to
test,
will
pass
the
same
thing.
Cup
charge
and
guru
can
expand.
The
generation
group
magenta
to
test
will
pass.
B
Everything
is
good.
Those
two
two
extensions:
they
expanded
my
chapter
task
a
little
bit
different.
They
do
not
touch
as
the
item
the
one
single
action
group
and
by
this
it
means
that
if
in
magenta,
I
have
15
tasks
which
uses
those
action
groups,
it
means
that
all
this
15
that
will
be
expanded
by
this.
B
So,
let's
see
an
example,
how
it
will
help
those
two
extensions
to
work
properly.
The
same
situation
have
much
amplitude
has
written
with
action.
Group
growth
of
this
expansions
they
extended
a
chapter
to
task
is
possible,
we
good,
but
what
will
happen
with
to
a
fantastic
caption
test?
What
I
do
suggest?
B
All
extensions
should
also
use
if
possible,
if
there
is
a
magenta
to
action
groups,
please
use
them,
because
if
you
extend,
you
and
other
extension
expands
magenta
to
actually
group
whatever
a
chatter
action
you
using
your
extension,
it
will
get
all
of
the
extensions
from
different
modules
without
knowing
each
other,
though
that's
the
magic.
What
I
wanted
to
share
with
you
guys?
B
That's
why
it
is
important
to
write
all
tasks
with
action
groups,
because,
as
you
know,
marketplace
is
forcing
and
advertising
everyone
to
start
writing
those
tasks,
because
at
some
point
of
time
they
will
build
an
infrastructure
where
they
will
run
your
extension
tasks
in
more
and
better
future.
They
go
wrong,
even
combinations,
different
functions.
You
avoid
such
problems
where
your
test
payment,
just
because
you
cannot
be
dependent
on
other
expansion,
please
I,
do
make
use
of
this
best
practice.
B
This
is
pretty
much
it.
If
you
have
any
questions,
please
raise
them.
I
will
try
to
answer
it.
It
actually
shouldn't
be
questions
about
action
groups.
It
can
be
any
question
about
Emma
Kiev
about
meetings
we
want
to
make
with
you
guys.
Maybe
you
have
some
suggestions.
Maybe
you
want
to
share
something
with
you.
Just
go
ahead
and
share.
Ask.
C
B
B
Yes,
we
can
verify
not
all
of
Magento
test
rating
reduction
groups-
yes,
I
know,
and
that's
just
because
I
was
laid
to
share
with
everyone
this
best
practice
and
explained
that
this
is
very
important.
So
that's
my
bad.
We
will
work
on
refactoring
those
tasks.
If
you
like
to
help
us
with
or
practice
your
skills
of
right
and
immediate
tasks,
you
can
go
ahead
a
minute
professor,
but
that's
an
example
which
actually
you
need
delivered
on
MPF.
B
We
have
migration
project
and,
as
you
can
see
only
in
before
and
after
which
our
work,
recommendations
and
postconditions,
you
can
see
single
are
actions
like
finding
some
magenta
CLI
command,
but
the
test
body
is
completely
reading
the
national
groups.
First
of
all,
what
it
gives
you,
your
cost
is
much
more
readable
and
you
can
find
how
faster
understand
what
is
going
now
here
by
reading
what
action
groups
using
first
action
group
is
obvious
stuff
from
open
contact
us
page
action.
So
it
tells
you
what
this
section
will
do.
B
Then
the
second
action
group
right
after
this
we'll
go
and
check
that
capture
visible
in
this
form,
and
we
will
try
to
feel
contact
us
for
pop
ciao
and
by
reading
this
arguments
will
pass
in
there.
You
can
see
that
we're
trying
to
feel
this
part
with
Ron
capture,
which
means
we
will
check
that
it
works
properly
right
after
we
filled
our
form
with
clicking
submit
button,
and
then
we
ascertain
contact
us
for
the
message
that
we
see
incorrect
capture
message
and
message
type
should
be
wrong.
B
Then
we
go
that
one
more
time
that
touch
is
feasible
and
the
second
time
we'll
fill
this
form
with
the
same
data.
But
now
we
pass
correct,
correct
culture,
pre-configured
culture
well,
and
then
we
see
that
we
submit
we
submit
our
form,
and
then
we
see
that
our
that
we
see
success,
message
that
we
are
that
we
submitted.
B
No
most
most
of
the
guys
when
they
started
to
write
production,
work
reduction
group
space
thought
that
this
action
groups
should
cover
everything
with
this
that
there
is
no
sense
to
create
action
groups
with
one
or
two
small
actions
which
easy
to
write
easy
to
copy/paste.
They
started
to
write,
really
big
pieces
of
code,
especially
it
was
read
product
and
one
single
action
group.
They
started
who
opening
page
action.
They
started
with
open
tabs
in
product
form.
B
B
What
I
figured
when
I
wrote
I
do
suggest,
write
actual
roses,
which
interacts
only
with
one
one
single
page.
If
your
action
group
is
started
to
do
some
actions
on
two
different
magenta
pages,
that's
that
should
be
a
marker
for
you,
a
flag
that
hey
I,
do
something
wrong:
I,
probably
need
to
split
those
action
groups
into
two
pieces.
So
here
we
can
see
that
we
have
a
straightforward,
simple
action
groups
with
which
just
opens
a
page
and
then
waits
for
the
dis.
B
Page
is
loaded
and
it
was
someone
some
extension
will
want
to
add
any
other
weight
or
page
law
or
expansion
would
like
to
have
some
steps
like
way
for
my
concrete
block
as
wallet
or
something
like
that,
he
will
be
able
to
express
one
single
action.
Room
and
all
past
which
go
into
this
page
will
be,
will
work
properly,
a
really
expanded
program.
B
The
other
first
half
is
yeah
and,
as
you
can
see,
I
forgot
to
tell
you
I
forgot
to
tell
you
that
we
finally
have
this
functional
test
to
finally
have
a
wank
here
in
my
chapter
technical
guidelines,
where
we
started
to
write
the
most
crucial
roles
and
which
helps
which
helps
the
MIT
F
test
clean
and
look
good.
Initially,
we
started
with
simple
rules
like
naming
conventions
or
each
MIT
F,
and
he
some
best
practices
which
must
work
must
be
in
our
something.
You
must
not
do
so.
B
B
B
B
Yeah,
this
section
group
is
also
pretty
small
by
this
prefix.
You
can
understand
what
this
section,
what
purpose
the
section
grooves
the
section
view
the
server,
so
this
is
going
to
be
a
concern
heard
that
capture
visible
on
contact.
Ask
for
me,
though,
as
you
can
see,
we
have
here
wait
for
element
visible.
We
do
sometimes
instead
of
writing.
Action,
which
called
C
sees
some
step
key
tags
by
some
selector.
Instead
of
this
sometimes
or
C
element.
B
Because
of
this,
we
give
a
chance
to
mention
to
applaud
and
show
this
government,
so
we
write
wait
for
element
visible
and
if
in
30
seconds
by
default,
if
I'm
not
mistaking
it
was
30
seconds
if
in
30.
Second,
this
element
is
not
appeared.
Test
will
fail,
saying,
hey
I
wasn't
able
to
find
this
element
after
30.
Second
wait:
oh
that's
why
we
use
wait
for
Ellen,
but
once
this
element
is
visible,
it
goes
next.
B
G
B
Wait
for
element,
visible
works,
very
simple,
that's
just
a
loop
which
checks
is
this
element.
Can
I
see
this
element?
If
it
says
no,
then
it
goes
one
more
time
can
I
see
this
element.
No,
and
this
loop
is
working
for
30
seconds
by
default.
Once
we
first
time
saw
this
element
than
we
are
going
out
of
this
loop
and
proceeding
with
past,
but
what
kind
of
selector
you
could
there?
It
doesn't
matter.
H
F
F
B
B
For
this
section
a
say
this
context
for
all
of
this
element
before
all
of
this
element,
I
had
in
a
contact
form
which
makes
this
the
length
or,
in
general,
wholesome
much
more
stable,
and
it
probably
won't
change
or
that
has
probably
not
cause
less
possible
to
have
one
more
input.
Capture
name
contact
us
with
in
contact
for
context.
But
if
I
will
remove
this,
it
gives
more
chances
to
appear
to
different
fields.
Come
check
fields
on
a
page,
so
I
always
try
to
find
a
context
for
all
my
selectors
and
also
the
other
practice.
B
Why
do
I
suggest
you
use
it
because
this
name
attribute
is
used
by
Magento
code
merchants,
ugly
in
itself,
so
probably
unlike
in
100%,
but
probably
99%-
sure
that
there
is
forming
a
post
request
which
contains
an
array
with
this
capture.
Contact
asked:
is
those
keys
are
used
by
mentioned
application
and
imagine
a
situation
when
a
developer
and
okay
I
want
to
change
this
name
after
you
to
contact
us
read
and
not
with
underscore,
but
with
it
will
not.
B
It
will
probably
not
do
this
because
he
will
see
a
lot
of
references
image
of
the
code,
this
every
key.
He
will
think.
Okay,
I'm,
crazy
I
won't
do
this
so
this
this
select
cover
this
name
and
will
leave
much
more
water
than
any
other
viewers,
because
not
always
ideas
is
used
by
merchants
application
to
understand
point
this
element
to
do
in
Magento
application.
So
if
you
work
with
input
fields
or
any
other
fields
which
has
the
name
attribute,
please
use
name
attribute
or
defining
selector.
Even
if
you
have
any
ignore
it.
That's
my
suggestion.
B
B
B
B
If
you
are
sure
that
your
page
contact
us
form
will
always
contain
capture
if
this
modules,
oh,
yes,
is
much
better.
Do
this
to
expand
that
action
just
by
specifying
say
my
name
and
write
into
an
action,
but
in
case
of
capture
there
is
always
a
case
where
you
open
this
form
and
puter
trust
you
and
do
not
want
to
verify
that
you
are
a
human.
B
So
sometimes
this
capture
field
can
appear
sometimes
do
not
so
I
created.
Another
action
group
called
of
the
class
born
with
cop
and
I'm
extended
basic
merchants.
Actually,
that's
something
you
need
when
you
when
you
start
thinking
about
it,
just
isn't
always
if
your
extension
or
your
module
is
installed
in
my
childhood.
Is
it
always
gonna
show
this
field,
or
is
it
always
changing,
behavior
of
some
form
or
some
page
or
something?
If
yes,
then,
do
not
use
this
expand,
not
ready
and
just
extend
this
time,
much
interaction,
but
if
you
know
that.
B
B
So
that's
that's.
Your
test
will
look
like
actually
have
your
customer
waking
us,
which
chose
this
I,
have
a
test
which
goes
fill
customer
again,
for
this
is
basic
customer
action
groups
and
we
pass
arguments
all
customer
only,
but
we've
already
informed
with
incorrect
password
with
not
existing
even
gentle
system.
So
we
will
see
wrong
message.
B
We
will
do
this
three
times
and
on
the
fourth
time,
I
believe
if
we
are
using
another
action
which
also
all
filled
customers
when
informed
with
capture
action,
so
we
we
know
that
we
will
be
doing
three
times
in
correct
credentials,
login
attempt-
and
we
know
that
after
this
three
attacks,
we
should
Eve
capture
phone.
We
know
this
river
and
we
have
three
different
action
groups.
B
F
But
one
thing
I
would
do
you
want
to
point
out,
since
we
did
have
a
question
on
selected.
I
was
thinking
about
this.
We
do
have
a
page
on
that
ducks
now
are
the
new
give
guides
that
have
we've
been
writing
that
has
basically
a
advanced
guide
on
the
best
practices
about
writing,
selectors
and
stuff,
like
that.
B
If
you
will
go
to
magenta
deaf
dogs,
please
always
go
to
this
functional
acceptance,
testing,
MIT
F,
because
this
is
the
most
recent,
the
best
document
given
or
a
dysfunctional
test,
and
just
never
try
to
open
this
page
always
and
right
here
on
the
right
section.
You
will
see
that's
right,
and
here
you
will
have
very
useful
topics.
We
will
cover
all
of
these
topics
with
similar
meetings
which
shall
recorder.
We
will
share
them
on
YouTube
channel.
Please
subscribe,
but
like
right
comment
share
with
your
friends.