►
From YouTube: GitLab 12.7 Kickoff - Verify:Testing
Description
Issues for the 12.7 Milestone
Kickoff Page: https://about.gitlab.com/direction/kickoff/
Testing Vision Page : https://about.gitlab.com/direction/cicd/
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
The
first
item
I,
want
to
talk
about
today,
is
number
three
to
zero:
four
six,
which
iterates
on
how
the
unit
test
results.
Summary
widget
is
being
displayed
on
that
merge.
Request
page.
This
change
solves
the
problem
of
not
really
knowing
the
number
of
tests
that
have
failed
against
a
code
issue
versus
the
numbers
that
are
airing
out
four
incorrectly
written
tests.
We've
heard
an
experience
that
this
can
be
a
problem
when
new
tests
are
introduced,
and
this
helps
diagnosing
those
errors
easier
for
contributors.
A
Next
up,
we
have
number
two,
seven,
five,
nine
nine,
which
solves
the
problem
of
the
browser
performance
testing
module
in
a
merge
request
showing
up
for
any
degradation
in
the
web
web
browser
performance
metrics.
We
know
this
can
lead
to
a
busy
and
sometimes
long
merge,
request
page
without
adding
really
any
valuable
information
so
to
solve
this
we'll
add
an
optional
keyword
that
will
be
created
to
set
a
threshold
for
the
widget.
A
If
the
total
score
drops
by
a
value
greater
than
threshold,
the
widget
will
appear
and
if
the
keyword
isn't
used,
the
current
behavior
to
show
the
widget
on
any
change
will
continue,
because
this
is
an
optional
keyword.
There
will
be
no
need
to
change
or
get
lab
C
IML
with
the
release.
If
you
don't
want
to
use
the
keyword
and
things
will
continue
to
work
after
the
release.