►
From YouTube: GitLab 13.5 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
Today
we'll
be
previewing
a
couple
of
the
items
that
the
team
is
working
on
for
the
upcoming
13.5
milestone.
You
will
find
a
link
to
the
13.5
kickoff
page
with
links
to
these
items
and
the
verify
stage
direction
page
with
discussion
of
our
future
work.
In
the
comments
below
this
video,
you
can
always
reach
me
at
jheimbuk,
gitlab.com
or
through
comments
on
items
labeled
with
the
group
testing
label
in
the
gitlab
project.
A
That
might
pass
on
the
next
pipeline
execution,
and
this
is
frustrating
for
developers
and
it
definitely
slows
them
down
as
they're
trying
to
push
code
and
push
features
out
to
users,
so
they
can
get
value
so
to
start
to
address
this,
we'll
be
adding
some
data
into
the
application
about
test
failure.
History
in
two
places,
the
test
summary
widget
and
the
unit
test
report,
I'm
going
to
hand
it
over
to
juan
to
talk
through
the
user
experience
of
those
two
items
thanks.
B
All
right
so
yeah,
let's
start
by
checking
the
proposal
for
the
report.
B
So
the
idea
with
the
report
is
that
we
are
gonna,
be
adding
a
new
column
called
our
name
failed
before,
and
what
this
column
is
gonna
tell
the
users
is
how
many
times
have
that
particular
job
failed
in
that
particular
test
failed
in
the
last
14
days,
that's
more
or
less
the
idea
that
we
have
for
the
period
of
time
for
this
feature,
so
it's
gonna
tell
them
like
it
has
failed
20
times
or
three
times
or
two
times,
and
that's
gonna
give
them
a
pretty
good
idea
of
how
flaky
or
how?
B
How
common
is
this
failure
in
terms
of
of
the
pipeline
that
they're
executing
the
other
part
of
these,
as
james
mentioned,
is
showing
these
type
of
data
in
the
test
summary
specifically
in
the
mr
widget,
so
it's
very
similar
once
the
person
opens
an
mr
and
the
pipeline
runs.
The
user
will
see
in
the
test
summary
a
similar
message
telling
them
that
27
out
of
79
failed
tests
have
failed
more
than
once,
in
the
last
14
days
same
period,
same
things
and
on
expansion
of
that
widget.
B
They
basically
get
like
these
indications
of
how
many
times
it
has
failed,
particularly
for
each
of
those
tests.
So
you
get
the
the
summary
and
you
get
a
breakdown
of
the
tests
that
are
failing.
So
this
is
a
little
bit
more
narrow
and
gives
them
a
better
scope
of
what's
happening
in
their
tests
and
if
they
should
address
or
not
the
issues
that
they're
seeing
there
yeah.
That's
pretty
much
the
idea
back
to
you,
james.
A
Excellent,
really
great
work
on
those
designs
really
excited
to
see
this
finally
making
its
way
into
the
product.
As
always,
we
welcome
feedback
through
discussion
of
these
issues.
This
video-
or
you
can
always
email
me
at
jheidluck
gitlab.com
about
these
or
other
issues
in
our
testing
backlog.