►
From YouTube: GitLab 12.6 Kickoff - Verify:Test
Description
Issues for the 12.5 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,
is
number
three,
three,
seven,
four,
three,
our
MVC
for
graphing
code
coverage
over
time.
We
know
that,
while
the
code
coverage
value,
that's
provided
in
the
merge
request,
widget
and
on
the
project
badge
is
helpful.
There's
much
more
value
for
users
when
seeing
how
this
value
is
changing
over
time.
A
As
of
the
14th,
we're
still
finalizing
our
design
for
this
initial
change-
and
you
can
see
the
discussion
about
that
in
the
issue
itself,
we're
looking
forward
to
feedback
from
users
and
the
community
about
this
feature,
as
we
want
to
expand
the
ability
to
graph
data
from
tests
within
the
get
lab
interface.
After
this
MBC
second
item
number,
four
one,
four,
eight
nine
is
another
item
I
want
to
highlight.
That
brings
more
context
to
data
being
displayed
already
in
the
get
lab
interface.
A
In
this
case,
it
is
the
code
quality
report,
we've
heard
loud
and
clear
from
users
that
seeing
how
a
merge
request
changes,
code
quality
is
nice,
but
having
the
full
report
available
about
the
code,
quality
of
the
code
base
would
be
much
better
in
this
feature
we'll
be
presenting
the
full
code
quality
report
in
the
pipeline.
In
the
same
way,
the
security
report
is
made
available
today
we're
looking
forward
to
feedback
on
how
we
can
continue
to
provide
context
of
data
of
this
and
other
test
data
to
help
contributors
create
quality
changes
faster.