►
From YouTube: Testing UX / PM / Research Sync 2020-07-08
Description
In today's session we talk about next steps for Test Execution History, 13.2 and 13.3 designs and Juan's progress on making the MR Widgets easier to understand. I'm looking at you "Source branch only".
A
This
is
the
verified
testing.
You
xpm
research,
sync
for
July,
8th
jump
right
in
I'm
gonna
skip
over
the
read-only
item.
It's
just
follow-up.
From
last
weekend,
I
was
out
jump
into
the
research
issue,
I
opened
for
the
text,
execution,
history
or
ESI.
You
assign
that
back
to
me.
Thank
you.
I
just
wanted
to
make
sure
if
there's
anything
we
needed
handle
synchronously
that
we
took
today's
meeting
to
talk
through
that
real
quick
yeah.
B
For
sure,
I
also
added
a
comment
in
the
she
just
gonna
go
about
this.
So
next
steps
are.
We
need
to
start
our
screener,
so
you
can
start
in
that
template.
If
you
want
to
do
it
in
the
Google
Doc
first
we
can,
or
you
can
jump
right
into
Qualtrics.
If
you
want
to
do
it
that
way
to
whatever
you
feel
comfortable
with,
and
then
we
need
to
open
a
recruiting
request
issue
as
well.
That
all
goes
in
that
research
project.
I
do
know
that
Emily
just
posted
somewhere
on
the
slack
Channel.
B
That
July
is
super
busy
for
her
for
recruiting.
So
I
wasn't
sure
of
the
time
line
for
this.
But
if
we
can
tell
her
and
Rupert,
maybe
we
can
talk
to
them.
August
I,
don't
know
when
you
were
hoping
to
to
do
the
research,
but
just
know
that
she's
got
a
12
studies,
she's
trying
to
balance.
So
it's
it's
a
lot
and
and
if
you
intend
to
do
any
other
recruiting
yourself,
you
can
say
that
and
the
issue
and
tell
her
she
doesn't
have
to
help.
A
C
C
A
C
A
C
I
do
yeah.
I
was
working
on
that
last
week.
I
have
some
doubts
that
I
need
to
ask
you
about
I'll.
Do
it
offline
I
mean
like,
but
otherwise
I
think
I
can
share
something
we
in
13.2,
one
that
we
can
basically
iterate
those
design
team
in
and
then
the
other
two
yeah
I'll.
Let
you
figure
out
that
I
think
that
I
saw
they
put
something
about
the
visual
mocks
today,
a
meeting.
So
maybe
that's
your
ideas
to
work
on
that
on
33
yeah.
A
C
A
A
C
All
right,
so
we
finally
got
merge
the
test
link
to
the
test
report,
which
is
awesome
because
that's
what
we
wanted,
but
something
happened.
Ricky
knows
that
it
wasn't
showing
in
production,
so
I
went
and
I
checked
out
and
yeah.
It
definitely
was.
There
was
a
column,
it
was
actually
in
production,
so
it
took
me
a
little
while,
but
I
figure
out
what
was
going
on.
It
was
like
something
that
we
couldn't
catch
in
review.
C
It's
the
way
that
the
pipeline
pub
is
being
passed
and
it's
we
had
some
things
that
was
making
not
sure
what
bar
I
fix
it
and
I
already
created
NMR
for
that.
So
hopefully
we
can
I
mean
it's
already
reviewed,
like
I,
think
we're
just
waiting
for
the
for
the
maintainer
to
review
it
emerge
it
so
I
think
it's
still
gonna
make
it
on.
13.2
is
just
we
have
to
yeah.
A
C
A
D
C
If
you
open
it,
it's
basically
it
right.
Now,
it's
kind
of
confusing
in
our
review
up
buttons
like
you,
are
and
review
one
open
to
the
app
and
the
other
one
opens
the
app
if
it
has
been
shown
a
review
tools
enable
and
if
it
doesn't,
it
opens
like
a
pop-up
like
modal
saying,
like
hey
how
to
enable
that,
and
that's
super
confusing,
like
people
I
remember,
complain
about
that
a
lot
that
one
is
not
part
of
the
epic,
though
right,
like
I,
just
like,
like
we
just
created
that
recently
yeah.
D
C
D
C
C
D
Know
if
you,
because
Marcel
is
still
tracking
the
effort,
if
this
could
not
be
like
implemented
by
you
or
by
you
know,
by
the
ingenuity
you
can
add
it
there
sure
it
will
be
counted
as
a
total
result,
if
not
the
so.
The
big
deal
all
the
main
important
part
of
the
correct
the
behavior
at
the
end
of
the
day,
and
it
sounds
like
yeah.
C
All
right,
I'll
figure
out
I
might
on
it
am
I
not
out
of
it
were
label
the
one
that
we
created
through
these.
If
I
don't
add
it
I'm
still
planning
to
work
on
it
and
if
I
get
to
these
on
30.2
or
13.3
I'm
gonna,
add
it
just
to
show
that
we
actually
like
just
like
track
him.
You
know
we
actually
did
these
and
improve
these.
So
it's
pretty
easy,
I,
just
I
just
think
we
need
to
figure
out
the
language
issues
they're
like
what
we
can
do
to
improve.
C
C
C
C
D
C
D
Text
or
other
improvements,
and
yes
something
that
we
have
talked
with
marsala
bar-
is
that
we
are
kind
of
like
tackling
all
of
those
things
separately
and
like
some
of
them
are
growing
into
the
bigger
items,
but
we
maybe
would
be
good
to
like
to
take
a
step
back
and
like
look
at
the
general
flow
of
the
user.
You
know
from
the
beginning
to
an
end
and
see
you
know
kind
of
what
makes
sense,
and
maybe
this
will
guide
us
some
decisions
so
yeah.
D
C
I
totally
agree,
I
think
my
my
Nissan
impression
I
just
changed
in
miles,
so
this
one
to
13.3,
but
my
initial
impression
is
that
we
probably
need
to
break
this
down
into
two
or
three
different
issues,
and
then
we
can
address
smaller
tactical
areas
of
this
language
problem
that
we
have
around
our
widget.
Someone
laughs,
I.
C
D
C
I
agree:
I,
don't
want
either,
so
maybe
we
should
do
that.
I
just
wanted
to
mention
that
initially
was
like
hey:
let's
fix
this
source
branch,
only
language,
and
then
you
realize
well,
but
what
we
also
have
this
problem
in
security.
We
have
it
on
accessibility.
We
have
em
test
and
like
on
the
metrics
report,
one
we.
C
We
also
have
like
the
way
that
will
show
other
things,
because
if
everything
part
is
part
of
the
same
problem
right
like
if
you're
gonna
change
from
one
text
like
you
gotta
change
the
other
one,
because
if
then
it
doesn't
make
sense
to
make
this
change.
You
know
like
especially
because,
like
it's
gonna
make
once
you
change
something
it
might
make
another
text
even
way
more
confusing.
C
C
A
C
B
So
I
am
going
to
probably
start
not
attending
these
weekly
meetings,
because
I've
got
to
start
carving
out
some
time
for
the
CI
adoption
journey
research
yeah,
but
please
ping
me
and
issues
or
slack.
If
you
need
me,
I,
don't
I'm
not
stepping
away
I
just
need
to
stop
going
to
every
meeting
that
I'm
three-week
and
you
guys
are
on
the
chocolate
Ella.