►
From YouTube: GitLab 13.10 Kickoff - Verify:Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Hi,
I'm
james
heimbuck,
the
product
manager
for
the
testing
group
in
the
verify
stage,
git
lab
today.
As
always,
I'm
joined
by
hayano,
the
ux
designer
on
the
team
and
today
we'll
be
previewing
some
of
the
work
the
team
is
going
to
be
doing
in
the
upcoming
1310
milestone.
You
can
find
a
link
to
the
1310
kickoff
page
with
links
to
these
items
and
the
verify
stage
direction
page
with
the
discussion
of
our
future
work
in
the
comments
below
the
video.
A
A
So
in
this
milestone,
the
theme
that
we're
kind
of
focusing
in
on
is
around
ux
improvements
to
some
of
the
features,
including
the
group
test
coverage
page
and
some
merge
request.
Widgets
and
hayana
is
going
to
talk
through
those
and
then
resurfacing
some
errors
from
the
junit
xml
parsing
that
regressed
at
some
point,
as
we've
been
working
on
that
project.
A
B
Yes,
let
me
start
sharing
my
screen,
so
you
can
see
the
items
we're
gonna
be
tackling
on
this
milestone.
There
you
go
so
one
other
thing
that
stood
out
during
the
ux
research
efforts
around
the
system.
Visibility
scale
was
visibility
of
system
status,
which
is
potentially
impacting
usability
the
most
today
in
our
product,
and
this
address
is
providing
users
with
additional
information
to.
B
So
this
milestone,
in
particular
we're
going
to
be
working
on
the
emphasizing
the
test
results,
icons
for
the
merge
request,
widget.
So
this
issue
in
particular
it's
about
making
some
of
these
icons
here,
less
permanent
on
the
ui,
so
that
users
can
consume
the
information
easily,
because
today
is
difficult
for
users
to
know
what
text
and
the
difference-
and
they
just
don't,
really
pay
a
lot
of
attention
on
the
context
of
the
copy.
B
But
they
just
look
at
the
the
the
green
icons
and
the
next
item
is
sorting
metric
reports
when
they
are
large,
when
there
are
large
numbers
of
merge,
request
metrics,
so
that
the
report
is
easier
to
read.
So
this
also
talks
about
consuming
that
information,
finding
what's
the
status
and
what's
the
most
important
when
it
comes
to
to
testing-
and
you
can
see
the
other
issues
that
we
are
tracking
related
to
these
specific
ar
that
tackle
visibility
of
system
status
for
testing.
B
So
we
are
collecting
everything
in
this
epic
to
stay
organized
so
back
to
you
james.
We
can
yeah
continue
the
conversation
thanks.
A
Hannah,
I
love
those
improvements
because
that
merge
request
widget.
The
test
summary
is
getting
just
unusable,
especially
in
the
gitlab
project,
with
hundreds
of
thousands
of
tests
being
run
in
every
pipeline,
so
that'll
be
a
great
improvement
for
us.
So
as
always,
we
welcome
feedback
through
discussion
in
these
issues.
This
video-
or
you
can
always
email
me
at
jheimbuk
gitlab.com
about
these
or
any
other
issues
in
the
testing
backlog.
Thanks.