►
From YouTube: User Centric Testing for 2020: How Expedia Modernized its Testing for the Web - Tiffany Le Nguye
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Pipeline
that
is
resilient
to
change.
So
in
expedient
group
we
have
thousands
of
developers
and
millions
of
users
every
day.
Our
changes
have
to
be
airtight,
easily
we're
factorable
and
consistent
to
use
in
the
world
all
over
the
year
at
the
north
and
skeeter
around
for
the
past
two
years
now
I
was
it
was
built,
a
user
centric
testing
suite
that
is
now
the
standard
at
Expedia
I
wanted
to
share
how
you
could
also
build
one
following
a
lot
of
the
philosophies
that
we've
adopted
in
person
thing
web
interactions
are
quite
complex.
A
Accessibility
is
a
priority,
especially
if
you're,
a
company
that
wants
to
follow
accessibility,
guidelines
and
legal
guidelines
and
performance
is
essential
as
well.
Updates
also
will
always
keep
us
on
our
toes
make
certain
libraries.
How
point
have
confidence
that
these
changes
won't
cause
unwanted
side
effects,
while
minimally
burdening
deaths
so
that
they
can
move
on
for
word
and
make
new
things.
I
want
to
walk
through
of
a
modern
and
and
testing
suite,
which
puts
users
first
for
a
maintainable
and
scalable
code
base.
A
At
the
end
of
this,
you
should
be
able
to
identify
who
your
users
are
and
test
for
their
individual
needs,
while
balancing
cost
and
confidence
in
your
systems.
It's
also
to
be
noted
that
the
text
used
within
Expedia
are
we
presented
our
specific,
but
the
philosophies
can
be
used
for
which
other
testing
frameworks
that
you
have
in
place
so
that
that
sound
annoyed,
maybe
a
little
bit
into
a
little
bit
of
an
intro
on
me.
A
So
I
took
me
and
I
am
an
engineer
at
Expedia
group
and
also
any
speaker,
yeah
and
I've
been
an
engineer
there
for
maybe
the
past
two
years
and
I
work
mainly
on
the
UI
platform
teams
there,
and
also
on
building
my
new
page
of
the
syllabus
that
you
look
up
when
you
are
googling
top
ten
hotels
of
man,
so
I
am
also
a
mentor
for
a
fika
camera
and
I
wanted
to
founders
technically
a
starship,
but
I'm
not
ready
to
get
that
rest
and
that's
about
that's
about
it.
For
me.
A
All
right,
let's
go
into
what
a
good
testing
pipeline
is
for
us
again.
Testing
Python
is
one
that
captures
unintended
changes
affecting
your
users.
It's
also
one
that
gives
you
confidence
that
production
won't
break
with
new
changes,
does
promoting
a
culture
of
quality
and,
finally,
one
that
provides
quick
and
effective
feedback
to
your
developers.
This
means
that,
when
something
breaks
you
want
to
be
immediate
into
knowing
why
that
happened
and
immediate
into
how
to
fix
it.
A
A
Can't
me
have
a
test
that
was
able
to
cash
that
something
has
changed
on
the
page
for
our
beautiful
natural
man
bent
bend
national
park
image
for
the
place
with
one
of
the
screen
on
frog.
This
is
something
that
might
affect
the
user.
Maybe
they
don't
wanna,
be
searching
for
a
tiny
more
in
a
place
that
has
screaming
frogs.
So
this
is
this.
This
is
a
little
bit
debatable,
but
other
examples
would
be
for
if
freaking
out
what
the
date
picker
did.
A
A
Here's
an
example
of
initially
the
same
page,
but
now
we
see
that
it
was
actually
am
each
one
wrapped
with
a
dip
for
a
dis,
dis
heading,
and
then
there
was
a
change
made
by
the
developer
and
what
he
did
is
they
just
removed
the
div,
because
they
saw
was
her.
Then
there
was
no
change
that
was
visible
or
affecting
the
user.
However,
the
test
still
broke.
This
is
a
bad
catch,
its
fragile
and
noise
developers
and
discourage
refactoring
with
this
and
it's.
A
Lot
of
this
follows
a
philosophy
of
testing
us
who
a
lot
of
you
may
know
as
the
creator
of
test
testing
library,
or
we
have
testing
library
and
also
a
phenomenal
speaker.
So
he
tweeted
out
saying
Des
Moines.
Your
tests
resembled
a
way
to
yourself
where
it's
used
to
more
confidence
to
give
me-
and
this
is
a
philosophy
that
I
want
you
all
to
keep
deep
in
your
hearts,
because
it's
the
one
that
just
one
to
be
following
us
all
throughout
this
pipeline.
A
A
A
All
right
so,
who
would
you
say,
are
the
users
of
this
page
with
this
wizard?
They
are
all
of
our
customers.
So
this
is
anyone
that
wants
to
come
in
they're,
gonna,
wanna
search
and
enter
your
dates
and
search
for
properties,
no
matter
how
what
kind
of
accessibility
needs
that
they
may
have?
If
you
need
any
any
more
reasons
to
handle
accessibility,
use
cases
and
follow
the
accessibility
guidelines
under
dentist
to
do.
There
is,
of
course,
a
lot
of
data
showing
that
it's
actually
good
business-wise
to
to
handle
and
support
these
these
customers.
A
B
A
On
people
that
are
going
to
be
coming
to
our
pages
and
giving
us
a
score
making
sure
that
we
have
good
rankings
and
we're
following
all
the
proper
carcasses
as
well,
what
they
want
is
good,
metadata
performance
and
accessibility.
This
is
very
important
to
us
I
just
video,
because
we
want
to
make
sure
that
we
are
recognized
possible
search
engines,
okay,
not
into
the
brass
tacks.
We
have
here
the
pike
when
does
most
common
expedient.
A
Initially,
we
start
with
static
checks,
so
things
are
any
checks
that
are
running
while
you're
programming
or
well,
while
you're
programming
or
before
you're
you're
clicking
code,
such
as,
if
you're
having
tech
script
or
any
lenders.
That
would
make
sure
that
you're
catching
any
really
cunning
mistakes,
for
example,
forgetting
to
use
forgetting
to
initialize
a
variable
before
using
it.
And
before
you
push
your
code,
then,
as
you
go
up
into
the
pipeline,
once
you
submit
at
Flores,
then
you
jump
into
a
lot
of
tests
that
we
wouldn't
run
in
parallel.
A
Keep
in
mind
that
there
is
a
serving
performance
at
hand,
keep
in
mind
at
the
top
really
really
fast.
You
have
community
region
tests,
which
you
don't
need
to
be
running,
an
entire
application
to
run
your
tests.
Then
you
have
the
intent
test
which
are
actually
building
rendering
and
then
going
on
an
actual
browser
in
order
to
test
your
application,
which
of
course,
is
slower,
Sigma
synchronous
and
can
also
be
a
little
bit
flaky
here
as
well.
A
And
finally,
you
have
performance
and
accessibility
tests
as
well
as
any
other
tricks
that
you
might
have
these
depend,
but
for
performance
of
it
says
tests
that
we
use
in.
It's
quite
slow
because
you
are
again
having
to
run
your
application
and
run
DS
lakehouse
for
performance,
a
sensibility
tests
on
each
one,
and
it
has
to
go
through
the
entire
Dom.
We're
going
to
talk
about
this
a
little
bit
more.
Well
a
lot
more
detail
in
the
following:
slides.
A
A
It
gives
us
when
you're
going
as
you
can
see,
as
you
can
see
from
the
previous
graph
as
you
go
more
into
testing
delete
a
user
with
an
actual
device
and
how
do
an
interactive
the
page,
then
you
get
into
something
that
gives
you
more
confidence,
but
it's
also
much
slower
and
more
expensive.
Expensive
can
be
monetary,
but
it
also
means
that
it's
something
that
will
cause
people.
A
B
A
Our
tests
visit
duration,
it's
a
little
bit
hard
to
define
what
integration,
what
our
unit
is
and
what
an
integration
is
inside
of
UI
code.
In
most
cases,
we
try
to
avoid
those
terms
and
kind
of
decide
your
functional
tests
or
they're
allowed
to
creation
tests,
but
there
is,
of
course,
use
cases
for
two
or
unit
tests,
and
then
we
go
to
muna
static
tracks
as
well,
which
do
cover
a
lot
of
these
pieces.
B
A
A
If
you
cannot
change
your
tools,
then
trying
to
be
mind
that
user
centric,
the
lots
of
use,
been
talking
about
here
and
go
forth
with
what
you
have
so,
if
you're
from
units
best,
for
example,
this
would
be
checking
the
input
label
and
all
image
start
inside
the
document
and
in
fact,
I
was
getting
set
as
well
as
overseas,
for
example,
taking
a
hint
out
the
wizard.
Oh
we
had
beforehand.
A
We
can
check
that
the
inputs
and
the
images
are
on
the
Dom
by
checking
dental
a
was
there
or
checking
and
also
tracking
down
our
image
to
screaming
frog
is
there
by
its
alt
text.
Another
example
would
be
checking
data
track
events
or
second
click,
sorties
number
one.
Here
we
are
going
to
get
the
button
by
the
search,
then
by
its
text,
search
and
we're
gonna
click
on
it
and
then
once
that's
done,
we
are
just
going
to
check
that
it
has
been
called
the
track.
Events,
half
and
cone
with
the
proper
earnings.
A
Other
examples
would
be
checking
air
states
from
that
customer
input
and
by
care
responses.
If
you
want
to
cover
SEO
in
here
and
have
metadata
as
you
can
also
check
that
or
check
that
and
the
public
tags
exist
as
well.
If
you
wanted
to
do
this
here
in
the
White
House
stage,
as
you
can
see
here,
these
are
pretty
good
at
covering
and
accessibility
guidelines.
A
It
makes
it
so
that
excessively,
you
know
not
an
act
of
God,
and
it
is
something
that
your
developers
can
get
used
to
as
well.
Other
examples
would
also
be
entering
dates.
Yes,
anything
here
really
is
where
you
would
have
too
many
different
experiences
that
your
user
would
have
as
much
as
you
can
really
and
we
have
end-to-end
tests
and
that's
when
you're
actually
building
in
running
app
locally
or
in
a
CI
a--
and
interacting
with
the
page
to
a
user.
A
B
A
An
actual
browser
we
also
use
Cypress
testing
library
for
additional
service
commands
that
would
match
the
adjustments
that
I
showed.
Previously,
let's
go
into
an
example
in
here
we
are
going
to
be
doing
what
I
just
said:
we're
going
to
find
a
check-in
and
checkout
dates,
and
your
arts
and
click
on
December
and
then
make
sure
your
diet
gets
some
of
us
to
de
crédito
raw
wood,
a
quick,
correct,
query
pounds.
A
B
A
These
tasks
have
been
done
and
we
can
click
send
by
finding
the
button
and
clicking
it
once
they've
done
that
it's
going
to
check
that
the
path
name
and
massage
has
been
changed
correctly,
so
that
it
has
gone
to
a
different
URL
that
has
hotel
search
in
this
in
this
case
and
was
given
the
proper
check-in
and
check-out
date,
it's
all
very
human,
readable
and
very
easy
to
go
through
and
see
how
it
is
that
broke
as
well.
I
want
to
show
here
an
example
of
how
Cyprus
would
be
run.
A
You
can
see
that
it
was
able
to
read
its
test,
maybe
go
visit
to
a
page
and
then
actual
browser
will
be
open
for
you
to
interactive.
This
is
for
development
purposes.
It
makes
it
very
easy
to
be
by
the
visitors,
a
console
that
you
can
interact
with
as
well,
and
it
shows
you
step
by
step
the
test
running
and
what
happens
once
it
gets
to
each
each
step.
In
this
case
it
went
in
and
went
we
were
out
and
found
some
inputs
typed
in
it
and
made
sure
that
the
bottoms
changed.
A
Don't
have
visual
regressions
most
smaller
applications.
Don't
need
this.
So
that's
something
to
keep
in
mind
it's
useful
when
you
have
external
UI
libraries
and
when
you
have
applications
that
you
do
really
want
to
check
any
UI
changes
that
might
have
cosmic
side
effects
for
doesn't
know.
A
visual
regression
test
is
one
that
compares
the
base
image
to
a
new.
B
A
Sure
that
never
no
differences
between
them
in
this
reference,
so
we
have.
We
have
as
page
that
says,
welcome
to
updog
with
the
dot
then,
once
there
was
a
change
to
change
each
dog
to
a
candy
cane.
This
image
was
taken
showing,
where
were
two
pixels,
that
change
we're
pretty
sure
that
the
app
did
not
mean
to
change
the
dog
dog
into
it,
and
now
we
know
that
that
did
happen.
A
And
visual
art
fashion
is
really
making
sure
that
those
those
unintended
side
effects
are
intentional
and
not
just
having
updated
a
library
and
maybe
not
realizing
that
it
propagated
to
some
little
page
down
below.
We
use
Cypress
again
14
the
screenshots
and
we
use
Cypress
screenshot
discs
for
matching
speed,
shots
and
emotion,
running
visual
disks.
A
A
B
B
A
B
A
Have
a
lot
of
polyfills
everywhere,
don't
make
sure
that
code
is
compatible
cross
browser.
There's
a
lot
of
static
tooling,
that
you
can
use
to
ensure
that
you're
not
using
API
start
missing
polyfills
such
as
the
Atlantic
planning
compact,
and
if
you
really
are
in
a
position
where
you
need
or
want
to
use.
A
Sorry
use
cross
browser
and
device
testing,
then
you
should
still
make
it
only
a
small
part
of
your
your
testing
pipeline,
because
that
typically
would
mean
that
you
need
to
use
browser
stack
so
that
were
very
selenium
and
that
is
extremely
flaky
and
has
a
lot
of
weeks
and
it's
very
difficult
to
do
tester
and
develop
so
shouldn't
really
not
be
the
bulk
of
occasion
or
a
matter.
You're
suspect.
That
being
said,
our
applications
are
typically
large
enough
and
have
enough
users
that
we
want
or
need
it
for
a
few
of
our
any
spaces.
A
B
A
From
deploying
history,
false
positives,
that
is
about
it,
so
there's
a
lot
more
to
this
topic.
Each
section
of
this
would
probably
need
some
talk,
but
left
a
time
that
we
have-
and
this
is
kind
of
to
give
you
an
overview
and
hopefully
give
you
an
idea
of
what
you
should
be
looking
out
for
when
building
and
testing
Atlantis
was
any
of
the
text
you
could
apply
for
them.