►
From YouTube: GitLab 13.2 Kickoff - Verify:Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
Code Coverage Data for Groups - Design: https://gitlab.com/gitlab-org/gitlab/-/issues/215104/designs
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
A
You'll
find
a
link
to
the
13.2
kick-off
page
with
links
to
this
item
and
the
verify
stage,
Direction
page
with
discussion
of
our
future
work
in
the
comments
below
the
video.
You
can
always
reach
me
at
Jaihind
buck
at
get
lab
comm
or
through
the
comments
on
the
items
we'll
discuss
today
or
any
item
with
a
group
testing
label
in
the
kit
lab
project.
So
today
the
item
I
want
to
highlight
is
really
a
group
of
items.
A
It's
some
work
that
the
team
is
doing
to
extend
the
code
coverage
graph
that
we've
recently
completed
we've
heard
from
customers
that
have
many,
even
thousands
of
projects
that
getting
any
metric
of
code
quality
to
measure
across
their
organization.
It's
really
hard
to
do
in
the
gait
lab
interface.
A
lot
of
them
have
resorted
to
gathering
code
coverage
data
by
hand
from
each
project
or
creating
their
own
custom
tooling,
to
get
the
data,
that's
really
only
half.
A
The
problem,
though,
is
then
they
have
to
turn
that
data
into
a
visualization
for
consumption,
so
in
1392
the
team's
going
to
be
starting
on
a
new
feature
that
will
gather
code
coverage
data
from
across
projects
in
a
group
put
it
all
into
one
easy
page
for
review
and
visualization.
So
one
is
going
to
walk
us
through
the
latest
designs
for
that
feature,
one
take
it
away.
Ten.
B
B
Ideally,
what
we
want
to
achieve
with
these
is
expose
as
much
valuable
data
key
stakeholders,
and
that
comes
in
several
flavors,
like
the
amount
of
projects
with
test
the
percentage
of
test
coverage
across
different
projects,
the
total
number
of
coverages
and,
of
course,
also
the
ability
of
drilling
in
specific
projects
and
analyzing
how
the
data
when
it
comes
to
testing
it's
divided
across
each
project
right.
So
in
30.1,
we
took
it
to
the
task
of
designing
these
things.
B
We
gather
some
feedback
from
internal
stakeholders
and
now
in
13.2,
we
continue
with
a
new
iteration
of
these
designs,
in
which
word
what
gonna
try
to
explore
better
affordances
for
showing
these
designs
and
continue
building
the
foundation
design
foundation
that
it's
gonna
be
used
by
the
current
work
that
are
doing
by
the
engineering
team
in
13.2,
so
yeah.
If
you
wanna
see
more
details
of
design
just
is
it
issued
twenty
one?
Fifty
one
forty
and
you
can
see
the
evolution
of
these
designs
in
thirteen
point,
two
back
to
you.
James
thanks.
A
One
so,
as
one
said,
you
can
review
those
designs
that
we
looked
at
today
and
the
epic
which
I'll
link
to
and
the
specific
issue
that
has
the
designs
in
it.
As
always,
we
welcome
feedback
through
discussion
on
that
issue
or
any
issues
through
this
video
or
you
can
email
me
at
J
hi
buck
at
get
lab
calm
about
this
or
any
other
issue
in
our
testing
backlog
thanks.