►
From YouTube: Testing UX / PM / Research Sync 2020-06-17
Description
Today's session was a discussion on how the MR beautification aligns with a Product Key Result, discussion on how to proceed with researching where/how to display test history and how Sahara sand is coming for Texas.
A
A
So
we're
like
a
third
of
the
way
now
through
the
quarter,
because
it's
13,
1,
13,
2,
13
3,
are
the
milestones
that
fall
in
the
quarter.
We
have
from
the
mr
beautification
project
some
issues
that
potentially
feed
into
this.
I
don't
know
how
related
the
two
things
are.
This
is
also
on
my
agenda
with
my
manager
for
tomorrow
of
hey.
A
We
have
some
mr
work
already
that
we're
planning
for
thirteen
one
or
four
thirteen,
two
thirteen
three
based
on
that
other
project
just
wanted
to
see
if
those
two
things
are
in
alignment
or,
if
they're,
completely
separate
issues
that
aren't
aware
of
each
other
just
trying
to
get
some
visibility
and
alignment
on
these
two
things.
So
I
wanted
to
show
this
key
result
to
the
group
and
ask:
are:
are
you
all
in
the
loop
on
this,
or
should
we
try
to
combine
these
efforts
a
little
bit.
B
A
B
C
B
B
A
A
A
So
this
is
one.
This
is
the
one
that
you
and
I
talked
about
yesterday
about
talking
about
user
story,
mapping
and
talking
through
the
process
of
how
somebody
goes
about
getting
data.
We
don't
think
is
necessarily
the
right
step.
It
feels
like
we've
already
validated
this
problem.
We've
talked
to
customers,
they
want
history
of
test
execution
for
a
number
of
reasons.
A
I
think
where
we
want
to
follow
up
either
through
customer
interviews
or
like
a
user
journey
map
session
or
talking
to
internal
stakeholders
even
of
how
they
would
use
this
and
we
could
dog
food,
it
would
be.
What
do
you
do
with
the
data?
That's
not
something
that
we
necessarily
expose
completely.
I
feel
like.
I
need
to
go
back
through
the
notes,
but
if
there's
there's
something
in
the
back
of
my
mind,
going,
we
don't
know
yet
what
we're
going
to
do
with
this
data.
A
D
C
One
go
oh,
I
was.
I
was
just
saying,
like
the
way
that
we
have
been
doing
it.
I
like
it
like
the
way
that
we
just
go
into
like
a
spreadsheet
and
we
start
like
defining
what
we
believe
is
the
right
path.
You
know,
I
wonder
if
you're
what
you're
asking
some
if
there's
something
that
works
for
more
than
the
two
of
us,
is
that
what
you're
asking.
A
Well,
it's
like
before
we
take
that
step
of
doing
the
story
map.
I
want
to
better
understand,
I
think
the
job
to
be
done
here
of
okay.
We
heard
and
we
validated,
I
need
test
history,
but
I
need
to
go
back
and
see
if
maybe
there's
just
a
nugget
there,
because
I
wasn't
focused
on
test
history.
We
were
focused
on
the
test
coverage
or
the
code
coverage
at
that
point
that
we
really
focused
in
on.
What
are
you
going
to
do
with
the
code
coverage
number?
A
Is
it
akin
to
what
you're
doing
with
code
coverage
where
you're
rolling
it
up,
or
is
it
something
more
at
the
the
level
of
the
engineering
manager
where
they're
then
assigning
tasks
out
based
on
that
test
execution
history,
or
is
this
really
a
developer
job
that
they
need
to
see
test
history
just
to
better
understand
the
problem?
So
I
would.
I
would
propose
that
we
take
those
two
paths
which
I
think
maps
up
on
what
you-
and
I
were
talking
about
a
little
bit
yesterday
in
the
first
one.
C
Yeah
that
makes
sense.
I
I
took
some
time
yesterday
to
research
a
little
bit
more
and
try
to
find
insights,
online
and
services
that
are
attracting
that
problem.
I
I
definitely
found
a
handful,
so
I
mean
that's
another
thing
that
we
can
yeah.
We
can
use.
You
know,
because
it's
it's
a
problem
that
it's
not
necessarily
specific
to
like
the
experience
of
github.
It's
just
like
a
general
problem
in
devops
and
yeah,
like
in
the
way
that
you
do
like
cis.
You
know
literature
like
plenty
of
like
resources
online
to
understand.
A
A
Yeah,
I
thought
I
had
the
links
to
I'm,
maybe
I'm
on
the
wrong
one.
There's
a
jenkins
plug-in
that
I've
been
shown
by
multiple
customers
who
are
trying
to
transition
over
from
jenkins
for
ci.
That
shows
just
a
very
basic
chart
of
all
of
the
previous
jobs
that
have
run
or
the
previous
builds
that
have
run
and
all
of
the
tests
and
if
they
passed
failed
or
were
skipped
and
the
ux
on
it
is
just
not
great,
but
that's
specifically
what
they're
asking
for
is
a
view
like
that.
A
So
what
I
want
to
better
understand
is
what
are
you
doing
with
that
data,
and
I
think
I
have
that
in
my
notes,
but
if
not
we'll
revisit
with
those
customers,
because
I
want
to
better
understand
their
problem
and
give
them
ux.
That
is
not
really
bad
so
that
we
can,
you
know,
exceed
expectations.
There.
B
That
helps
with
a
little
bit
of
context,
I
think
you're
asking
great
questions
and
yeah.
If
we
feel
like
we
don't
have
clear
answers
to
that
yeah,
I
think
it's.
The
proposal
that
you
gave
is
an
amazing
start.
Yeah
yeah,
I'm
not
sure.
Are
you
asking
about
like
any
specific
processes
around
that
it
sounds
like
you've
been
doing
that
in
the
past,
as
well
already
like
curious,
how
could
we
help.
A
Yeah,
I
think
where
we
need
to
just
revisit
is
a
little
bit
of
the
problem.
Validation
and
I
just
I
thought
in
my
mind
I
was
like
oh
we're
done
with
problem
validation,
so
we
need
to
start
in
design
and
solution
validation.
But
we
really
haven't
finished
problem
validation
on
this.
So
we
need
to
move
it
back
into
that
state
finish
that.
C
B
And
you
know
like
I'm
so
glad
to
hear
that
james,
that
you
are
the
one
who
is
like
pulling
the
break
a
little
bit
and
say:
hey,
you
know
like
it
sounds
like
we
need
to
do
a
bit
more
problem
validation
because
I
see
often
like
well,
it's
so
easy.
We
always
tend
to
jump
into
the
solution,
validation
and
like
making
thinking
solutions
but
yeah.
I
I'm
so
thankful
that
you
are
saying
okay.
B
Maybe
we
need
a
little
bit
more
information
here
and
I
think
exactly
like
what
you
said
and
talking
to
internal
stakeholders.
We
have
so
many
people
who
have
using
that
in
gitlab,
and
maybe
if,
if
you
feel
like
well
talking
to
outside
users
from
outside
of
gitlab,
is
always
also
useful
because
they
have
a
bit
of
a
different
perspective
and
I
think
yeah,
emily
and
maybe
lori
can
help
us
finding
those
people.
A
Well,
I
think
it's
started
to
think
about
specifically
for
this,
the
showing
history
of
tests.
There
was
two
places
that
we
could
put
it
and
an
mvc
can't
go
into
two
places,
so
it
was
for
me,
it's
like
all
right.
Well,
we
better
understand
who's
going
to
use
it,
how
they're
going
to
use
it,
what
their
flow
is
to
use
it,
and
we
didn't
have
answers
to
that
question.
A
So
that's
why
it's
like
hold
on
hold
on
like
we
could
build
feature
parity,
but
I
don't
know
if
that's
really
what
customers
want,
even
though
that's
what
they're
asking
for,
I
don't
know
if
that's
the
right
thing
to
go,
do
right
now,
cool
all
right.
What's
everything
for
me,
juan
laurie
nadia,
any
other
topics
to
discuss?
B
Nothing
for
me,
I
just
wanted
to
say
if
you
need
any
help
around
the
mr
beautification
or
improvements
or
enhancements.
Let
me
know,
as
I
was
saying
earlier,
I
was
grateful
to
see
how
other
product
managers
and
product
designers
been
responsible
to
this
effort.
This
is
great.
I
know
marcel
and
federal
are
doing
a
lot
there
and
also
thanks
a
lot
for
doing
the
recording
together.
I've
seen
a
lot
of
great
comments
in
multiple
stages,
like
when
people
see
that
pm
and
ux
are
doing
that
together.
B
A
A
C
Right,
I
did
it,
I
didn't
have
anything
in
the
gym.
I
just
have
one
update
I'll,
be
pushing
new
design
iterations
for
the
group
coverage,
maybe
later
today
or
tomorrow
and
so
yeah,
just
probably
being
some
of
you.
Of
course
you
james,
but
now
nadia
also
love
your
feedback
from
that,
because
you
already
saw
those
designs
and
I'm
basically
iterating,
based
on
based
on
things
that
we
discussed
before
so
yeah.
I'll,
probably
thank
you
as
well.
D
D
It's
not
exciting,
but
apparently
it's
blowing
from
the
sahara
all
the
way
across
the
atlantic
to
texas,
florida
and
louisiana
so
good
times,
wow
yeah
yeah.
Last
time
this
happened
like
I
just
won't.
I
haven't
gone
outside
very
much
anyway.
You
know,
but
the
last
time
I
would
wheeze
and
just
feel
like
horrible,
and
nobody
knew
what
it
was
until
we
realized
that
the
sand
had
come
so
santa's
coming
again,
so
juan
stay
inside.