►
From YouTube: GitLab 13.7 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
Issues discussed on the call:
https://gitlab.com/gitlab-org/gitlab/-/issues/271077
https://gitlab.com/gitlab-org/gitlab/-/issues/270102
A
Hi,
I'm
james
heimbach,
the
product
manager
for
the
testing
group
in
the
verify
state
agent,
git
lab
today
I'll
be
previewing
just
a
couple
of
the
items
the
team
is
working
on
for
the
upcoming
13.7
milestone
you'll
find
a
link
to
the
13.7
kickoff
page
with
links
to
these
two
items
and
the
verify
stage
direction
page
with
discussion
for
future
work.
In
the
comments
below
the
video,
you
can
always
reach
me
at
jheimbuk,
gitlab.com
or
through
comments
on
any
of
the
issues
with
the
group
testing
label
in
the
gitlab
project.
A
This
release
for
testing
is
going
to
be
focused
on
delivering
some
maintenance
work.
That's
going
to
enable
us
to
build
some
exciting
new
features
in
upcoming
milestones,
as
well
as
fixing
some
bugs
that
were
discovered
in
our
recently
released
feature
around
group
code
coverage,
so
the
first
enhancement
that
we'll
be
tackling
is
some
maintenance
on
the
comparison
logic
for
the
code.
A
Quality
merge
request,
widget
this
change,
along
with
the
creation
of
a
new
pipeline
artifact
of
that
diff
that
drives
the
widget
is
going
to
enable
us
to
build
a
view
of
code
quality
violations
in
line
in
the
merge
request.
Diff
view,
it's
very
similar
to
the
work
that
the
team
has
already
done,
alongside
a
community
contribution
for
showing
test
coverage
in
that
merge,
request
diffu.
So
we're
really
excited
about
this,
and
we
can
build
on
that
view.
A
I
also
want
to
talk
about
a
bug
that
we'll
be
fixing
in
the
group
code
coverage
page.
We
discovered,
with
the
help
of
a
customer,
that
the
feature
is
reliant
on
the
default
branch
in
a
project
always
being
named
master,
and
we
know
that
many
users
are
changing
their
default
branch
names
and
so
we're
going
to
be
enhancing
this
feature
to
use
the
default
branch,
regardless
of
its
name
in
this
milestone,
so
that
you'll
always
see
data.