►
From YouTube: GitLab 12.9 Kickoff - Verify:Testing
Description
Issues for the 12.9 Milestone
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
CI/CD Direction: 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
Hi
I'm
James
I'm
buck
the
product
manager
for
the
testing
group.
In
the
verify
stage
you
get
lab
today,
I'll
be
previewing
a
few
of
the
items
the
team
is
working
on
for
the
upcoming
12.9
milestone,
you'll,
find
links
to
the
12.9
kickoff
page
in
the
verify
stage,
Direction
page
in
the
comments
below
the
video.
A
As
in
all
the
kpop
videos,
you
can
always
reach
me
at
Jake
I'm
buck
at
get
lab,
comm
or
comment
on
any
of
the
items
that
we
mentioned
here
today
or
any
items
with
the
group
testing
label
in
the
get
lab
project.
So
first
I
want
to
provide
an
update
on
an
item
that
I
talked
about
in
a
previous
kickoff
call.
Graphing
code
coverage
changes
over
time
for
a
project
and
first
I
want
to
thank
everyone
for
the
great
feedback
that
we
got
on
the
designs
and
the
direction
of
the
issue.
A
Overall,
the
teams
have
been
making
great
progress
on
this,
both
on
the
design
and
the
actual
implementation
front
for
the
feature
we're
getting
closer
to
making
this
happen
in
our
12
9
release,
you
can
see
those
updated
designs
in
the
design,
tab
on
the
issue
scroll
down
and
show
those
off
real,
quick,
we're
starting
to
use
this
design
tab
quite
a
bit
more
to
include
our
latest
designs.
You
can
always
find
the
latest
greatest
they're
from
our
designer
JJ.
A
This
is
going
to
extend
the
get
lab
UI
to
download
report
artifacts
without
having
to
incur
a
double
storage
penalty
of
the
file.
There
are
always
ways
to
make
artifacts
like
jinyu
new
results
available
for
download
and
to
see
the
test
results
in
of
the
unit
changes
in
the
merge
request,
but
you
have
to
store
that
artifact
twice
to
make
that
happen,
and
so
for
things
like
a
really
large
code
quality
report
that
can
be
kind
of
impactful.
A
So
this
change
will
both
streamline
the
setup
and
eliminate
that
double
storage
penalty
that
you
would
incur
to
get
both
the
report
fully
downloadable
and
to
see
the
change
in
the
merge
request
widget.
So,
lastly,
I
want
to
talk
about
number
606
one
in
an
issue:
I'm
pretty
excited
about
it's
to
display
screenshots,
alongside
j-unit
errors.
So
in
talking
with
our
internal
quality
team,
we
found
out
that
they
have
to
spend
a
lot
of
time
digging
through
screenshots
that
are
stored
as
artifacts
to
research
and
resolve
errors.
A
That
might
happen
in
our
end-to-end
tests
that
are
failing
so
to
make
that
easier,
we're
working
on
a
view
within
the
job
page.
It's
going
to
show
that
screenshot
that's,
captured
and
referenced
in
the
j-unit
output,
alongside
the
j-unit
error
from
the
metadata.
So
again,
as
with
the
other
one,
you
can
find
the
latest
designs
for
what
we're
thinking
about
for
this
issue
within
the
design,
tab
and
we'd
love
to
hear
feedback
on
these
designs
and
the
overall
direction
of
the
issue
to
make
sure
we're
really
on
the
right
track.