►
From YouTube: Repeat Failed Test Counter speedrun
Description
Speed run of the repeat failed test counter introduced in 13.8 showing how to see if a failed test has failed and how often on the default branch in the past.
Release Post: https://about.gitlab.com/releases/2021/01/22/gitlab-13-8-released/#repeat-failed-test-counter
A
This
is
available
in
all
tiers,
and
this
runs
in
the
test
summary
widget
on
a
merge
request,
so
it
does
require
merge
requests
today.
What
this
does
is
we'll
count
all
of
the
failures
of
a
test
over
the
course
of
14
days
on
the
default
pipeline
and
then
give
you
a
count
of
those
in
the
test
summary
we
understand
and
talking
to
developers
that
the
problem
with
failed
tests
is
you
don't
know
how
often
it's
failed
in
the
past,
and
so
this
is
our
first
implementation
towards
a
richer
test
history.
A
So
this
is
the
write-up
in
the
release
post,
and
I
just
want
to
show
a
quick,
mr
here.
This
is
an
mr
on
the
gitlab
project.
It
has
some
failed
tests,
and
here
in
the
test
summary
widget,
I
can
expand
and
see
a
bunch
of
the
failed
tests
that
are
running
in
the
different
jobs
and
if
I
get
into
this
rspec
system
11,
I
can
see
that
some
of
these
tests
have
failed
in
the
past
on
our
default
pipeline,
in
this
case
only
one
time
in
the
last
14
days.
A
So
I
don't
know
how
much
that
tells
me
about
how
flaky
this
test
might
be.
Generally.
The
default
pipeline
runs
pretty
well
for
us
or
the
default
branch
rather,
but
clicking
on
that.
You
can
get
some
additional
details
with
the
system
output
how
long
it
took
to
run
class
name
those
sorts
of
things.
This
is
going
to
expand
into
the
unit
test
report
incoming
release,
but
that's
a
quick
and
easy
way
to
see
how
often
a
test
is
failing
on
the
default
range.
Thanks.