►
From YouTube: Testing PM/UX Weekly - 2021-03-09
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
B
This
is
the
testing
or
this
the
verified
testing
ux
pm
sync
for
march
9th
2021
hayana,
and
I
were
just
discussing
what
the
next
steps
are
in
the
code.
Quality
diff
mr
design
and
the
design
issue
is
racked
up
as
of
1310
today,
yesterday,
really
next
steps
are.
I
will
update
the
implementation
issue
with
screenshots
of
the
figment
design
and
a
link
to
the
figma
prototype
as
well
for
the
front-end
folks,
and
then
we
can
start
breaking
down
that
work,
that
this
full
implementation
is
scheduled
for
14-1
11.
B
A
Yeah
and
I
just
wanted
to
align
with
you
james,
it's
is
my
approach
for
working
on
the
design
proposal.
I
saw
that
the
other
designers
they
use
the
the
upload
designs
feature
and
then
the
comments
happen
in
that
area.
I
prefer
to
use
just
a
link
to
figma
and
have
that
as
a
source
of
truth,
especially
when
we
change
so
many
small
things
in
the
ui
copy,
etc.
So
I
just
wanted
to
align
with
you
if
you're,
okay,
with
moving
forward.
A
B
Yep,
that's
fine
for
me!
If
that's
going
to
be
the
fastest
way
for
you,
especially
with
your
bifurcated,
isn't
the
right
word
because
it's
more
stratified
than
that
with
your
varied
workload,
then!
Yes,
let's
absolutely
do
what's
most
efficient
for
you,
I'm
going.
A
B
A
I
spoke
with
pedro,
and
indeed
we
we
have
to
change
that
as
in
we
just
have
to
give
context
on
what
that
dash
means,
and
we
talked
about,
for
example,
adding
a
tooltip
there
just
to
explain
the
meaning
of
that.
What
is
it
a
vulnerability?
A
What
do
we
use
it
for?
Because,
in
other
widgets,
we
also
use
to
convey
different
meanings?
Oh
yeah
metrics
license
compliance
browser
performance.
So
what
I
learned
with
what
I
aligned
with
pedro
was
that
we
shouldn't
look
at
what
the
other
widgets
are
doing.
We
fix
what
we
need
to
fix
for
testing
and
then
yeah,
the
designers
responsible
for
the
other
areas
in
the
merger,
quest,
widget
or
pedro
are
going
to
do
the
other
cleanup
and
since
we
know
what
else
that
we
know
also
that
we
can
use
new
status
icons.
A
A
Those
examples
we
should
see
if
we
can
reuse
some
of
this,
the
iconography
in
other
areas
of
the
oh,
perfect,
the
testing
area,
but
then
again
I'll
prototype
and
then
I'll
I'll
work
on
the
first
pass
with
pedro
to
see
if
it
aligns-
and
in
case
we
are
the
ones
dictating
what
the
ui
should
look
like
the
other
designers,
the
other
teams
would
potentially
follow
the
y
pattern
there
and
refine
on
the
emerging
five
widgets
as
a
whole.
Okay,.
B
So
do
you
have
a
preference
for
metrics
because
excuse
me,
because
we
don't
have
context.
B
So
if
I'm
looking
at,
let
me
share
my
screen
real
quick,
so
we're
looking
at
the
same
thing,
so
I'm
not
trying
to
describe
what
I'm
looking
at
again,
which
window
is
that
this
guy
okay?
So
we
have
these
two,
the
metrics
report
yeah,
which
we
use
the
neutral
icon,
because
we
don't
have
context
of
if
it
went
up
or
down
because
we're
just
doing
a
string
comparison.
B
So
even
if
you
see
that
the
string
is
smaller,
that's
not
necessarily
a
bad
thing
in
context
for
the
user
like
if
it
was
how
much
memory
is
this
taking
up?
Maybe
I
want
it
to
be
smaller,
so
that's
why
we,
it
was
my
assumption
is
because
I
don't
believe
I
made
the
decision
to
say:
hey,
let's
just
use
neutral
here,
so
this
one
we're
never
going
to
have
a
context
of.
Did
this
get
better
or
worse
and
then
browser
performance.
B
We
might
be
able
to
look
at
and
say
hey
this
got
better
or
worse,
just
assuming
that
smaller
numbers
are
always
better
and
there's
probably
some
nuance
within
that,
where
bigger
numbers
might
be
better
for
some
of
those
metrics.
But
we
know
what
the
metrics
are.
So
we
can
get
a
this
got
better.
This
got
worse
context
on
browser
performance
and
it
kind
of
looks
like
we
already
have
that.
Looking
at
the
example
there's
the
x
there
for
the
transfer
size,
one
where
the
amount
went
up.
B
So
I'm
thinking
that
that's
that's
already
built
into
that
widget
and
we
can
continue
to
use
neutral
or
we
can
swap
out
that
line
for
a
different
status,
icon.
A
So
exactly
if
you
open
the
other
link
where
we
talk
about
the
severity
yeah
this
one,
I
think
we're
gonna
have
to
go
with
something
that
resembles
or
or
we
reuse
some
of
these
icons,
okay
and
then
give
context
on
hover
or
something
because
that's
another
conversation
I
had
with
pedro,
if
we
add
a
different
icon,
we're
going
to
have
to
add
to
the
icon
set
for
gitlab
svg
and
go
to
the
whole
process
of
approval
validating
this
icon.
A
So
what
we
talked
about
is
that,
for
example,
if
the
severity
is
low
right,
I
think
we
use
the
the
grayed
out
icon
the
circle
yeah,
the
previous
one,
because
this
one,
the
one
that
has
two
rows
of
icons,
is
mostly
for
pipeline,
so
pass
failed.
B
Yeah,
so
we
don't,
we
don't
have
a
context
of
severity
for
the
metrics
report,
so
we
could
use
severity
unknown
for
all
of
them
yeah,
but
then
for
the
browser
performance
we
have
either
it
got
better,
it
got
worse
or
it
stayed
the
same
and
within
that
like
for
everything,
that's
getting
worse,
we
could
use
severity,
but
what
do
we
use
for
getting
better
yeah?
So
if
my
total,
like
total
score,
if
total
score
got
better,
I
don't
want
to
show
you
a
severity
because
that's
not
a
problem.
B
To
think
about,
as
we
look
at
this,
I
I
don't
remember
what
we're
using
on
our
test
summary,
mr
widget,
but
we
might
be
able
to
reuse
some
iconography
from
there.
That's
already
been
approved
for
like
the
test
now
is
passing
or
the
test
now
is
failing.
I
think
we
have
a
set
of
icons
for
that.
A
Yeah,
we
use
the
same
ones
severity
we
use
the
same
ones
today
they
are
being
used
for
the
merge
for
the
pipeline,
so
pass
fail
so
same
iconography.
A
I
understand
from
better
that
we
want
to
move
away
from
that,
so
we
want
to
standardize
so
the
the
the
secure
widgets,
the
testing
which
they're
all
going
to
show
the
same
icon.
So,
for
example,
you
severity,
but
in
different
ways
giving
a
different
context.
So
that's
why,
in
the
conversation
of
code
quality
in
the
diff,
that's
why
pedro
and
and
andy
were
talking
about
adding
a
label
next
to
the
icon,
saying
hey!
This
is
not!
This
is
a
you
know,
a
low
or
high
severity.
This
adds,
or
removes
my
goodness
words.
A
B
That
sounds
good
yeah.
We
don't
have
to
solve
this
right
now,
yeah
coming
up
with
pedro,
I
think
later
this
week
or
next
week,
and
he
and
I
can
talk
through
some
of
that
of
we
have
the
scale
for
code
quality,
but
everything
else,
there's
no
real
scale
of
severity
and
it's
more
of
a
granular
did
it
go
up?
Did
it
go
down?
Did
it
stay
the
same
yeah?
So
maybe
we
can
work
on
some
different
icons.
There.
A
Awesome-
and
let
me
see
this
is
already
my
priority
list
right.
I
think
this
is
the
next
one.
Oh,
not
no,
it's
actually
in
the
backlog.
I
think
the
next
one
is
the
the
visual
indicator
in
a
merger
quest
that
we
talked
about
yeah
blocking
the
emerging
class
local
coverage.
B
I'm
swapping
some
stuff
around
in
your
backlog.
I
just
moved
the
design
for
the
project
quality
dash
up
ahead
of
the
unit
test
report
stuff,
because
I
think
that
we'll
prioritize
how.
A
It
doesn't
change,
I
think
you
are
reordering
right,
but
yeah.
I
have
to
reload
the
page
to
see
what
has
changed.
B
B
B
Yeah,
I
think
that
we'll
we'll
stick
with
getting
the
ui
for
the
unit
test
screen
unit
test
report
with
screenshots,
so
that
front
end
can
move
forward
on
that
and
after
that,
it'll
be
that
global
dashboard
via
quality.
B
B
I
love
you,
I'm
just
really
really
excited
to
get
that
that
new
data
view
of
three
pieces
in
there
and
and
show
them.
I
think
that
that'll
be
a
great
feature
for
us.
B
A
B
Maybe
this
afternoon
I'll
bust,
the
ipad
out
and
the
pencil
and
start
to
sketch
it
out
that
way
it
does
it
at
all.
Look
like
any
sort
of
real
design.
It's
like
here's,
some
doodles
from
the
product
manager.
A
B
A
Not
so
much
this
week,
I
I
have
actually
my
fyi
item
here,
I'm
attending
conference
tomorrow
and
thursday,
so
I
have
yeah
limited
capacity
in
general.
It's
a
remote
conference
anyways,
so
I'm
gonna
be
in
front
of
my
computer,
but
I'll
try
to
yeah
stay
away
from
slack
for
a
couple
of
hours
tomorrow
and
yeah,
and
the
only
thing
I
would
like
to
align
is
actually
triple
check
because
we
already
spoke
about
this
last
week.
Is
the
system
usability
score
issues
and
maybe
the
q2
kr's
okay
rs4
for
us?
A
Where
is
that
issue?
Because
we
already
closed
that?
So
I
just
want
to
circle
back
and
and
talk
about
next
steps.
This
one
here.
B
B
A
A
B
Yeah,
okay,
so
yeah.
So
this
is
the
shared
qr
which
we're.
So
I
was
looking
for
the
q2
planning
issue
that
you
and
mickey.
B
Going
through
that,
I
closed
on
friday
and
looking
for
that,
and
then
that
would
link
up
to
jackie's
issue
that
she
started
to
make
sure
that
I'd
actually
put
our
krs
that
we've
gotten
together
into
that
list
of
hers.
But
now.
A
B
A
B
B
We're
just
not
yeah
okay
cool,
so
I
put
those
in
there
so
I
tried
I
just
kind
of
it
feels
like
I
watered
them
down
a
little
bit
and
made
them
very,
very,
very
broad.
As
far
as
key
results
go,
I
was
yeah
trying
to
get
away
from
a
punch
list
approach
that
we
weren't
real
keen
on.
B
So
I
just
tied
key
results
into
themes
and
went
from
there,
but
I
think
that
if,
if
we're
just
going
to
support
the
shared
sus
performance
kr,
we
can
do
the
same
thing
that
we
did
in
cube
one
and
say
great
we're
going
to
do
that.
We're
going
to
do
that
by
working
on
not
necessarily
the
issues
that
have
been
identified
for
us,
but
issues
in
widgets
where
we
want
to
move
our
performance
indicator.
B
A
Yeah
sounds
good
to
me.
I
think
it's
cool
good,
some
proactive
improvements
towards
the
usability
of
our
product
and
we
have
that
epic
right
for
usability
white,
app,
ui,
polish,
etc.
A
So
I
think
it
makes
sense
that
if
you're
working,
for
example
on
I
don't
know
the
specific
parts
of
the
mergerquest
widget
and
then
we
are
fixing
these
usability
issues,
if
it's
a
small,
a
quick
win
schedule
that
and
make
everyone
everybody
happy
lords,
the
the
shirts
sure
k
are
so
I'm
on
board
and
in
terms
of
jobs,
to
be
done
on
the
cms
research
for
a
category.
Do
you
already
have
an
idea
of
what's
going
to
come
up
next.
B
So
we're
working
on
code
quality
in
this
milestone
or
in
this
quarter,
I'm
hoping
to
get
that
done
in
q1.
I
think
it's
gonna
be
probably
around
usability
testing
and
figuring
out.
What's
going
on
with
visual
review
tools
and
if
there's,
if
there
continues
to
be
opportunity
there
or
not,
and
if
it's
opportunity
we
can
move
on
with
the
current
alignment
of
the
team
or
if
we
need
to
look
into
other
ways
of
augmenting
that
category.
B
I
think
just
usability
testing
specific
to
that.
The
visual
review
tools
feature
that
we
have
okay,
I
mean
as
a
product
person.
That
is
a
hugely
impactful
feature
that
I
think
that
there's
a
ton
of
opportunity
in
it.
The
research
that
we
want
to
do-
or
that
I
want
to
finish
up
in
q1-
is
around.
Why
don't
people
use
it?
Is
it
too
hard
to
set.
A
B
Is
it
not
as
valuable
as
we
think
it
is,
or
are
there
just
not
that
many
users
of
it
or
people
who.
B
Awesome
so
trying
to
work
through
that.
I
think
that'll
be
the
next
category
that
we
go
dive
into,
though
I
think
we
have
a
good
sense
of
the
other
categories
where
they're
at
and
where
the
next
things
are
to
to
move
them
forward.
But
visual
or
view
tools
is,
as
I
think,
about
what
we
want
to
be
dog
fooding.
It's
the
next
big.
A
B
B
A
B
Been
fine
yeah,
it's
been
good,
it
was.
It
was
tougher
than
I
expected
to
get
people
to
interview
for
the
last
round.
I
ended
up
using
some
developers,
but
some
quality
folks
like
it
was
a
very
pool,
and
that
was
an
internal
to
gitlab,
to
try
to
get
the
code
mature
code,
testing
and
coverage
maturity
to
move
to
viable.
B
It's
easier.
I
think
when
we're
recruiting
externally,
because
they
have
that
incentive,
but
I
think
that
there's
a
mixed
bag
there,
because
you
get
folks
who
maybe
aren't
as
familiar
with
github,
whereas
our
internal
folks
like
live
it
breathe
it
use
it
all
day.
So
you're
going
to
get
a
ton
of
great
feedback.
A
A
A
B
A
So
realigning
priorities
I'll
continue
with
things
in
the
stack
order,
the
one
or
what
quality
number
in
the
div.
The
merge
request
good
to
go,
so
you
can
close
that
one
issue
or
you
update
I'll.
A
Item
today,
thank
you
so
much
and
I'll
jump
to
the
visual
indicator
and
the
dash
icon.
Since
we
already
started
discussion
and
it's
a
small
change
that
in
a
way
relates
to
what
we,
what
we're
doing
for
the
overall
cleanup
of
the
merger
quest
widget,
that's
gonna
be
on
my
list
for
next
week.
A
A
After
my
after
my
class,
I'm
like
I
need
a
couple
of
hours
a
couple
of
hours
to
get
back
to
my
senses,
awesome
cool!
All
right!
I
see
you
later
thanks
for
the
chat,
have
a
good.