►
From YouTube: GitLab 13.12 Kickoff - Verify:testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Today
we're
going
to
be
previewing
work,
the
team
is
going
to
be
doing
for
the
upcoming
13.12
milestone
and
I'm
sharing
our
planning
issue
here,
as
you
can
see,
you'll
be
able
to
find
a
link
to
the
1312
kickoff
page
in
the
handbook,
with
links
to
the
items
to
talk
about
today
and
the
verify
stage
direction
page
that
discusses
our
future
work
in
the
comments
below
the
video.
A
So
today
we'll
talk
through
the
1312
planning
issue
a
little
bit
in
this
milestone.
The
team
is
going
to
be
focused
on
some
smaller
but
important
changes
that
are
related
to
test
coverage,
specifically
we're
going
to
start
work
in
on
a
feature
that
will
let
teams
require
a
merge
request
or
use
the
merge
request.
Approval
flow
if
overall
test
coverage
has
decreased
for
a
merge
request
if
it
was
merged,
we're
gonna
be
using
that
existing
merge,
request.
A
So
we're
going
to
just
give
them
a
little
bit
of
a
helping
hand.
We
always
show
that
test
tab
on
the
pipeline,
but
now
we'll
include
a
link
to
documentation.
If
we
see
that
no
test
report
was
uploaded,
that
includes
a
ton
of
links
and
examples
for
different
programming
languages,
of
how
to
create
the
test
report,
get
it
into
a
junit
format
and
then
upload
it
to
gitlab.
So
you
can
start
to
make
use
of
those
features.
A
We
especially
think
that
our
counter
identifying,
potentially
flaky
tests
is
something
that
a
lot
of
teams
are
going
to
find
useful
and
then
I
wanted
to
give
an
update
on
our
mvc
for
showing
code
quality
as
part
of
our
merge
request.
Diffs,
the
team
is
working
hard
to
wrap
that
up
in
1311
and
while
I
don't
have
it
listed
as
part
of
our
1312
plan,
just
a
breaking
change.
A
Yesterday
the
team
said
we
think
we
can
add
that
to
our
1312
milestone
the
full
implementation
annotating
in
line
the
code
coverage
or
code
quality,
rather
violations
that
were
found
as
part
of
the
mr.
So
we're
going
to
add
that,
as
a
stretch
deliverable
for
the
for
the
milestone.
So
while
we
don't
anticipate
shipping
it
in
1312,
we
do
think
that
it
will
be
available
on
gitlab.com
by
the
end
of
1312
and
then
we'll
introduce
it
to
all
users
in
14.0.
B
Welcome,
thank
you
james,
and
I
just
wanted
to
give
an
update.
As
you
know,
this
quarter
we
have
agreed
to
have
a
shadow
qr
between
ux
and
product
to
focus
on
usability
and
help
improve
the
visibility
of
the
system
status.
B
So
I
just
want
to
give
a
shout
out
to
the
testing
team
that
has
helped
us
so
far
to
implement
these
issues
I'll
link
here
the
list
of
open
items
that
we
do
have
for
this
quarter,
and
I
just
want
to
say
that
this
is
a
very
convenient
effort
right
that
pointly.
It's
also
good
for
business
goods
to
help
a
positive
impact
on
how
people
use
their
product
so
moving
towards
q2.
B
We're
going
to
keep
focusing
on
improving
the
usability
of
testing
and
all
other
game
club
features,
and
my
second
heads
up
in
the
update
is
that,
with
my
recent
recent
transition
to
the
product
design
manager,
role
for
ci
cd,
my
focus
has
switched
to
harry
a
product
designer
that
will
cover
my
role
in
testing
and
runner
and
will
be
a
new
new
hire
for
gitlab.
B
So
in
the
meantime,
in
13.12,
it's
all
right
where
I'm
going
to
continue
to
support
the
testing
team
by
facilitating
ux
review
of
merchant
requests
that
introduce
changes
to
the
user
interface
or
the
user.
Experience
of
our
testing
features,
and
this
will
help
us
have
a
conversation
that
is
focused
on
the
small
improvements
unblock
the
team
rather
than
being
involved
in
delivering
new
features
and
working
on
the
high
level
designs,
so
that
we
can
move
forward
with
the
improvements
to
that
thing.
And
let's
get
back
back
to.
A
Thanks
hannah,
it
has
been
a
pleasure
working
with
you.
We
will
miss
you
greatly,
but
we're
excited
for
you
in
your
new
role.
So
as
always,
we
welcome
feedback
through
your
discussion
on
these
issues.
The
video
you
can
email
me
at
jheimbuk,
gitlab.com
about
these
or
any
other
issues
in
our
testing
backlog.