►
From YouTube: Working through a UX review
Description
A GitLab Product Designer works through a merge request by using review apps to test the existing experience and the implemented change.
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95071
A
So
last
friday
I
was
tagged
to
review
this
change,
and
so
I
did
a
little
bit
of
homework
last
week,
but
I
wanted
to
record
most
of
the
review
today
so
up
front.
It's
telling
me
that
I'm
working
on
something
related
to
deployments
as
pertaining
to
environments
and
that
deployments
should
have
approval
options.
Users
can
view
previous
approved
and
rejected
comments.
A
A
A
A
A
A
A
C
A
A
C
A
A
A
C
A
A
C
A
A
I'm
going
to
do
just
maintainers,
I
mean
I
guess
I
really
could
test
developers
maintainers
and
like
they're,
just
they're
a
lot
of
roles
and
options
here,
and
I
honestly
I
don't
really
feel
like
it's
worth:
testing
every
single
case
like
maintainers
and
administrators,
checked
or
demo,
and
developers,
plus
maintainers
or
just
administrator
and
demo,
then
adding
the
user
like
there's
a
lot
of
different
options.
So
I'm
just
gonna
pick
one
and
hope
that
it's
extensive
enough
for
our
purposes.
A
B
A
A
A
A
A
A
B
A
C
A
A
A
A
C
A
A
C
A
A
C
A
C
A
D
D
D
Approve
or
reject
deployment
number
six
dialog
link
at
demo,
owner
approving,
will
run
the
manual
job
from
deployment
number
six
rejecting
will
fail.
The
manual
job
environment,
staging
deployment,
tier
staging
manual,
job
deploy
staging
current
approvals,
one
two
avatar
at
demo
owner
approved
two
minutes
ago,
cop
copy
branch
name,
copy
branch
name
banner.
Now.
D
Monitoring
middle
thought
in
lab
window
link
add
demo
owner.
You
are
currently
on
a
link
inside
of
a
dialog
to
click.
This
link
press
control,
option
space
to
exit
this
group,
press
control,
option,
shift,
link,
demo,
image,
review,
image,
review,
image,
review
approval
options,
approve
or
reject
clickbit
comment:
optional,
edit
eff
space
space
r
over
reject
but
approve
button.
You
are
currently
on
it
image,
review
image,
review
for
merge,
request.
A
A
So
I'm
not
going
to
test
all
the
functionality
again,
but
I
should
make
sure
like
there's,
no
weird
key
binding
issues
and
it
does
seem
like
the
main
focus
is
on
the
staging
page,
which
I'm
not
trying
any
other
additional
environments.
I
didn't
try
adding
a
dev
environment
or
a
pre-prod
or
a
canary
and
then
like
comments
and
production.
I'm
just
sticking
to
the
only
path
that
I
had
available
to
me
or
suggested
to
me
in
the
merge
request.
D
Enable
chrome,
e.g
link
spoken
image,
link,
link,
link,
stop
entering
table
link,
link
main
button
group.
You
are
currently
on
a
button
group
ins,
approval
options,
button
approve
or
reject
deployment
number
eight
dialog
link
at
root,
cancel
button
link
at
root
close
button
button
table.
Eight
columns,
link
success,
link
image,
administrate
button
approval
options.
You
are
currently
on
a
button
inside
of
a
cell
to
click
this
button,
press
control.