►
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
Hi
you
Express,
my
name
is
Juan
Ramirez
I'm,
a
product
designer
for
the
testing
and
runner
groups,
and
today
for
my
UX
Showcase
I'll,
be
talking
about
features
that
we
have
been
working
on
for
testing
called
past
screenshots
VIX
unit
reports
I
also
want
to
apologize
because
I
wasn't
able
to
make
it
to
this
meeting.
So
this
is
why
I'm
pretty
recording
my
presentation,
so
you
guys
can
watch
it
at
your
own
time
right.
So,
let's
jump
into
it.
So
let's
talk
a
little
bit
about
the
the
testing
group
for
context.
A
So,
as
you
know,
EC
ICD
testing
is
a
big
part
of
creating
a
continuous
integration
right.
So
even
at
the
very
core
of
the
definition
of
continuous
integration
and
continuous
delivery,
we
have
testing
as
part
of
that,
like
big
part
of
that.
So
usually
it
starts
with
you
know,
with
the
source,
then
build
then
test
then
deploy
right.
So
test
is
definitely
a
major
part
of
software
is
deployed
and
taryn
and
unmanaged.
So
it's
a
crucial
part
of
our
CI
experience.
A
Although
it
is
very
important,
we
are
still
not
meaning
very
minimal
levels
we
haven't
reached
yet
like
the
love
ability
of
other
areas.
So
we
have
a
lot
of
work
ahead
of
us
in
in
this
particular
feature
that
I'm
going
to
be
talking
about.
There's
many
things
that
apply
to
this
type
of
work
that
we're
doing
I
will
say
that
from
all
the
things
that
we
have
here
on
our
strategy,
I
think
it
applies
to
all
of
them
in
one
way
or
another.
A
But
definitely
it
applies
very
concretely
to
the
last
three
applies,
very
importantly:
persistent
testing,
which
is
a
area
for
2020.
It
definitely
has
a
lot
of
impact
in
usability
testing,
and
it
also
has
an
impact
on
accessibility
testing,
but
also
beyond
that
even
for
unit
testing,
our
load
testing
screenshots,
which
is
what
I'm
going
to
be
talking
about,
have
certain
implications
and
can
help
with
the
creation
of
those
we
with
enabling
things
within
the
testing
practices.
So
it's
a
very
crucial
part
what
we
are
doing
here
all
right.
A
So,
let's
start
with
the
initiative
goal
so
like.
Basically,
we
have
business
goal
and
we
have
the
interval
like
from
the
business
prepared
perspective,
but
what
we
want
to
do
is
basically
help
our
customers
to
troubleshoot
and
fix
test
issues
that
are
tied
to
be
showing
regressions
or
a
title,
rendering
problems
or
things
that
are
very
visual
that
happen
within
a
browser,
and
we
want
to
help
them
to
get
those
screen
shots
that
are
helping
them
to
to
fix
these
issues
in
a
very
low
friction
way.
A
We
hope
that,
eventually,
it's
going
to
be
as
capable
as
figuring
out
what's
going
on
on
the
on
the
screenshots
that
we're
taking
as
part
of
the
tests
and
then
from
a
user
goal
perspective,
it's
very
clear
what
we
want
to
do
with
this
specific
feature
well
want
to
do.
Is
we
want
to
help
our
customers
troubleshoot
pipelines
faster
and
especially,
we
want
to
help
them.
We
pipelines
that
have
visual
testing
and
have
web
rendering
jobs
and
because
those
are
the
jobs
are
generating
screenshots.
A
And
although
we
support
that,
currently,
it's
not
that
easy
to
try
and
find
other
resulting
screenshots.
It's
actually
very
painful,
and
that's
why
our
MVC
starts
by
putting
those
generated
screenshots
higher
in
the
GUI
and
like
remove
the
friction
that
currently
exists
when
trying
to
retrieve
them.
A
And
then
it's
gonna
take
screenshots
at
certain
points
or
certain
events,
most
likely
failures,
and
once
that
is
happening
within
the
job,
then
what's
going
to
happen
is
that
the
screenshot
is
going
to
be
stored
as
an
artifact
of
the
job.
So
the
way
that
our
customers
do
that
currently
is
that
they
go
to
the
job
they
navigate
to
the
job,
and
then
they
download
or
browse
the
artifact
directly
from
that
view,
and
that's
a
long
journey
with
a
lot
of
friction.
A
Usually
it's
a
sip
file
and
you
got
a
son
skip
things
and
you
got
to
do
like
a
lot
of
things
and
if
it's
browsable,
then
you
got
a
lot
drilled
to
folders.
You
don't
know
exactly
what
you're
looking
at
so
there's
definitely
a
lot
of
issues
with
that
process,
so
the
working
hypothesis
is
like
that's
not
the
way
that
it
should
be.
We
should
make
it
super
smooth
and
it
should
be
very
visual
as
screen
shots
are
so
the
working
hypothesis
is
quite
simple.
Is
we
want
to
present
this
in
a
rueful
way?
A
It's
in
a
in
an
area
of
the
sea
I
will
be
likely
as
a
dedicated
CI
view.
We
believe
the
people
were
running
webdriver
tests
with
frameworks
like
selenium
need
these
to
actually
be
productive
when
using
this
type
of
tools
and
there's
a
very
important
part
of
this,
which
is
what's
the
common
ground
and
the
common
ground.
Is
that
anyone
who
is
doing
this
type
of
work
or
this
type
of
testing?
They
are
likely
using
an
X
unit
framework
for
this.
A
So
we
got
a
build
on
top
of
that
and
the
idea
here
is
that,
like
anything,
that
any
job
that
is
generating
X
unit
report
or
X
unit
type
reports
should
be
able
to
consume
or
to
build
on
top
of
the
system.
And
then,
basically,
we
should
be
able
to
consume
from
those
orbs
and
show
these
images
in
the
smooth
way
and
then
finally,
I
think
the
most
important
thing
here
to
understand
is
cut
the
process
of
downloading
the
artifacts
and
process
of
retrieving
those
screenshots
shouldn't
be
hard,
but
it's
probably
even
more
than
that.
A
A
So
if
you
have
its
own
living
area
where
it
can
interact
and
figure
out,
what's
going
on
with
the
tests
that
are
failing
or
the
tests
that
are
producing
screenshots,
alright,
so
the
way
that
we
approach
this
is
basically
we
kind
of
like
didn't,
do
the
right
process
or
like
the
common
process
in
developed.
This
is
already
kinda
like
a
validated
problem,
so
our
problem
validation
wasn't
the
most
like
conventional
problem
validation.
We
already
have
existing
community
feedback
and
designs.
A
We
had
customers
who
actually
created
mocks
and
put
those
marks
in
an
issue
which
is
the
originating
issue
for
this
problem,
and
we
have
that
evidence,
but
we
also
have
a
lot
of
strong
internal
use
cases
for
these
in
our
develop
projects.
So
so
we
have
from
week
from
the
beginning,
we
had
a
very
validated
problem
that
required
a
solution,
so
basically
the
way
that
we
did.
A
This
was
gathering
all
that
feedback,
revalidating
action
problem
with
stakeholders
and
then,
basically,
based
on
those
marks,
we
said
like:
let's
use,
marks
and
jump
to
solution,
validation
and
there's
a
lot
of
other
related
issues
about
this
particular
problem.
I
put
some
some
examples
there
and
there's
also
a
lot
of
external
external
data
validation
coming
from
many
places.
You
can
just
go
on
like
google,
this
and
you'll
see
that
like
actually
these
matters
to
customers
and
developers
in
general,
so
the
solution,
validation
research
was
quite
simple.
A
There
were
a
couple
of
marks
provided
by
the
community,
basically
doing
a
little
bit
of
what
they
wanted
already.
So
we
said:
okay,
like
we
already
have
something
that
we
can
just
go
and
show
someone.
So
we
took
those
marks
provided
by
the
community,
and
then
we
did
some
qualitative
research.
We
because
we
have
such
a
strong
internal
stakeholder
case
with
these,
we
basically
have
interviews
with
internal
customers,
so
we
show
them
these.
A
We
went
through
a
very
extensive
discussion
guide
to
explore
the
can
wide
breadth
and
depth
of
the
problem,
and
then
we
got
a
lot
of
information.
I've
got
a
lot
of
positive
feedback.
This
is
the
right
direction
for
this
feature,
but
we
basically
got
major
feedback
in
four
areas.
One
was
the
importance
of
like
summarizing
things.
You
know
showing
that
there's
that
something
happened
and
what's
the
context
in
general,
of
the
things
that
happen
right.
A
The
second
thing
is
exploring
a
possibility
of
having
both
a
role
lock
and
a
screen
shot
combined
because,
like
sometimes
people
don't
want
to
go
up
between
all
those
things
back
and
forth
and
then
specifically
out
improvements
and
then
information
presentation,
improvements
as
well.
Alright,
so
the
design
phase,
the
design
phase
was
very
interesting
because,
basically,
the
way
that
we
did
it
was
like,
we
think,
a
big
design
right.
We
went.
A
We
created
these
new
CIP
you
without
feature-rich
view
with
filters
with
session
filters,
with
status
filters
with
ability
of
hiding
paths
and
like
standing,
screenshots
and
doing
many
things,
but
yeah.
Eventually,
we
figured
that
this
was
a
good
conversation
starter,
so
we
basically
put
these
and
we
try
to
get
feedback
from
the
initial
participants
and
other
stakeholders.
We
got
a
lot
of
positive
feedback
and
but
then
we
realized
that
we
actually
had
to
bring
down
that
to
an
MVC.
A
So
while
the
designs
that
we
created
initially
solve
a
problem
or
solve
the
problem
very
extensively,
we
needed
to
basically
broom
down
things.
I
was
version
of
it.
So
we
what
we
did
was
we
went
through
a
user
journey
mapping,
exercise
we
team,
and
then
we
redefined
the
embassy,
and
then
we
came
up
with
the
most
essential
aspects
of
this
feature.
A
So
what
we
end
up
doing
was
rethinking
a
little
bit
the
things
and
then
the
big
major
thing
that
happened
here
is
that
we
decided
that
this
feature
makes
more
sense
when
it's
living
at
the
pipeline
level
and
not
at
the
job
level-
and
this
makes
sense
because,
like
you,
might
have
several
Suites
generating
screenshots
and
you
really
wanna
have
those
screenshots
aggregated
in
an
easy
way
that
is
consumable
and
very
easy
to
parse
on
and
digest
right.
There
are
some
sacrifices
that
we're
making.
A
We
don't
have
the
initial
summarization
aspect
of
the
feature
and
we're
sacrificing
in
other
areas,
but
respect
to
get
back
to
those.
We
basically
are
doing
here
and
exercise
in
which
we
are
bringing
to
the
customer.
The
most
essential
features
as
an
MVC,
and
this
is
the
result
so
some
design
highlights
are.
A
But
the
difference
is
you
just
do
it
from
here
without
rolling
into
the
actual
job?
We
also
found
some
out
of
scope.
Issues
like
the
usability
of
the
tabs
in
the
pipeline
view,
is
reaching
a
ceiling,
so
we
might
need
to
figure
out
that
down
the
road.
We
have
an
existing
test
tabs
that
outline
all
the
executed
tests,
so
we
believe
that
caroli
overlaps
a
little
bit
so
eventually
we'll
need
to
merge
both
features.
A
We
have
at
some
a
small
design
iterations
coming
especially
some
layout
of
the
table.
Maybe
it's
going
to
change,
but
we
respect
fix
this
during
12.8
and
then
work.
It's
going
to
be
happening
in
front
and
it's
going
to
be
happening
in
12.9,
and
then
we
we
basically
expect
to
ship
Deason
in
12.9
and
then
there's
many
other
initiatives
are
deriving
produce
from
this
specific
initiative.
A
A
Alright,
that's
pretty
much
it
I
was
come
trying
to
run
through
it.
Why?
But
yeah
I
just
want
to
thank
everyone
who
has
been
involved
in
this
project
and
was
give
give
feedback
for
these
I
really
appreciate
it.
I
also
want
to
give
thanks
to
Rory,
who
provided
very
valuable
feedback
for
the
discussion
guide
in
our
research
and
yeah
I
hope
you
enjoy
learning
a
little
bit
about
testing
in
good
luck.