►
From YouTube: GitLab 13.9 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
Issues discussed on the call:
MR Usability: https://gitlab.com/gitlab-org/gitlab/-/issues/293730
Test History on Unit Test Report: https://gitlab.com/gitlab-org/gitlab/-/issues/235525
A
B
B
Okay
sure,
as
I
started
boarding
the
testing
group,
my
focus
would
be
on
improving
the
test.
Summary
widget
in
the
merge
request
page.
We
want
to
solve
some
of
the
existing
usability
issues
and
also
help
users
differentiate
the
content
that
is
being
displayed
there,
so
that
there
is
low,
there's
less
confusion
and
they
can
quickly
solve
detected
issues
and
shift
features
with
more
confidence.
So
that's
my
focus
for
now
and
yeah
back
to
you.
So
we
can
hear
more
about
the
milestone,
focus.
A
Yeah,
I'm
excited
about
these
ux
changes.
So
it's
easier
to
see
when
you
expand
that
test
widget.
I
know
especially
on
the
gitlab
project,
with
the
100
000
tests
that
we
have
when
that
expands
it's
hard
to
tell
what
is
a
test.
What
is
the
job
where
anything
is
broken,
so
this
little
subtle
improvement
is
going
to
be
a
huge
one.
I
really
appreciate
the
work
on
that
cool,
so
today
I'll
be
previewing.
A
One
of
the
items
the
team
is
working
on
for
the
upcoming
39
milestone
you'll
find
a
link
to
the
13.9
kickoff
page
with
links
to
this
item
and
the
verify
stage
direction
page
with
discussion
of
our
future
work
in
comments
below
the
video.
You
can
always
reach
me
at
jheimbuk,
gitlab.com
I'll
leave
my
email
in
the
comments
or
through
comments
within
the
issues
with
the
group
testing
label
in
the
gitlab
project.
A
So
today
this
is
going
to
just
start
with
our
planning
issue
for
13.9
a
couple
of
top
priorities
for
us.
The
one
I'm
going
to
be
talking
about
today
is
our
next
iteration
on
the
test
history
mvc,
taking
the
work
that
we've
done
in
the
test,
summary
widget,
which
hayana
just
showed,
and
the
team
is
going
to
be
working
on
the
ux
for
over
into
the
full
unit
test
report.
A
So
it's
taking
this
view
where
we've
taken
the
trace
out
of
this.
This
is
some
older
design
into
a
pop-up
or
into
a
modal
window,
but
adding
the
status
here
or
not
only
the
status,
but
the
field
before
text
there
so
be
something
very
similar
to
what
you'll
be
seeing
soon
in
the
test
summary
widget,
showing
how
often
a
test
is
failing
on
that
default
branch
over
time.
So
you
as
a
developer,
can
get
a
sense
of.
Is
this
a
one-off
failure?
A
First
time
it's
happened
in
two
weeks,
or
is
this
continually
flapping
back
and
forth
likely
a
flaky
test?
Maybe
we
should
go
quarantine
it
or
spend
some
time
fixing
it
so,
taking
that
same
view
taking
it
to
another
part
of
the
ui,
so
that
if
you're
not
using
merge
requests
but
you're
running
tests
in
the
pipeline,
you'll
be
able
to
get
that
view
there
as
well.