►
From YouTube: GitLab 14.5 Kickoff - Verify Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
MR Widget Working Group: https://about.gitlab.com/company/team/structure/working-groups/merge-request-report-widgets/
Issues Discussed:
https://gitlab.com/gitlab-org/gitlab/-/issues/223793
https://gitlab.com/gitlab-org/gitlab/-/issues/263723
A
Hi,
I'm
james
heimbach,
the
product
manager
for
the
testing
group
in
the
verify
stage
of
git
lab
and
today
I'll
be
previewing
the
work
the
team
is
going
to
be
doing
for
the
upcoming
14.5
milestone,
you'll,
be
able
to
find
a
link
to
the
14.5
kickoff
page
with
links
to
these
items
and
the
verify
stage
direction
page
with
discussion
of
our
future
work
in
the
comments
below
the
video
and
we'll
link
to
all
the
issues
that
we
talk
about
as
well.
A
You
can
always
reach
me
at
jheimbuk,
gitlab.com
or
through
comments
on
the
issues
with
group
testing
label
in
the
gitlab
project.
I
also
have
with
me
today
gina
doyle,
our
wonderful
product
designer
for
the
testing
team
and
I'm
already
sharing
the
14-5
planning
issue.
So
let's
detail
some
of
the
work
that
we're
going
to
be
working
on
during
this
milestone.
So
a
couple
of
things
I
want
to
call
out
in
14-5,
the
team
is
continuing
to
focus
on
the
liability
and
performance
related
to
build
artifacts.
A
We
find
that
when
you
run
a
large
number
of
pipelines
and
jobs
and
create
a
lot
of
artifacts,
you
can
really
quickly
run
out
of
storage,
even
if
you
have
very
short
default
expiration
values
and
until
now,
if
you
did
run
into
that
problem,
you
would
have
to
either
wait
for
those
artifacts
to
expire
and
not
be
able
to
run
pipelines
or
through
the
existing
jobs.
Api
delete
those
individually
job
by
job.
You
can
just
delete
a
whole
bunch,
so
this
new
endpoint
is
going
to
let
users
delete
all
of
their
artifacts
at
once.
A
This
is
a
very
much
a
minimum,
viable
change.
It's
really
a
great
class
or
a
big
hammer
type
of
approach
and
we're
going
to
be
iterating
in
future
milestones
to
make
that
experience
better
a
little
bit
more
fine
green.
To
give
you
better
experience
beyond
just
deleting
every
single
artifact
and
I'll
link
to
the
iteration
issues
that
we
have
in
the
description
below
and
then
one
other.
Actually,
I'm
going
to
hand
it
over
to
gina
to
talk
about
our
usability
issues
and
some
of
the
research
that
we're
doing
on
the
ux
side.
B
Okay,
great
yes,
there
is
some
work
happening
on
the
group
code
coverage
graph
today.
If
you
want
to
know
how
many
projects
were
part
of
a
day's
coverage
value,
it
required
downloading
the
data
and
inspecting
it
manually
and
it's
a
slow
process
to
understand.
What's
going
on
in
your
projects,
so
we'll
be
adding
the
projects
and
jobs
with
coverage
that
went
into
the
coverage
value
to
the
tooltip
on
the
graph
to
make
getting
that
data
faster
for
more
users.
B
In
addition
to
the
research
project,
we
have
a
lot
of
movement
going
on
right
now
with
merge
requests
widgets,
where
we
have
a
working
group
that
has
been
set
in
the
that
spans
across
the
gitlab
company,
and
the
group's
goal
is
to
implement
the
new
mr
widget
designs
that
were
provided
by
the
ux
team
across
all
of
our
merge
request.
Widgets
and
a
lot
of
those
are
in
the
testing
group.
B
A
Thanks
gina
yeah,
I'm
really
excited
about
all
of
that.
The
jobs
to
be
done.
Research
is
great
because
it
helps
us
find
problems
in
the
workflow
and
not
just
try
to
build
the
new
shiny
features
but
solve
for
problems
that
the
customers
really
have
and
try
to
get
their
stuff
done.
So
it
really
helps
me
create
a
great
roadmap
for
how
we're
going
to
get
to
that
next
maturity
level
and
I'm
excited
about
the
mr
widget
stuff
as
well.
A
It
makes
just
such
a
cleaner
view
and
it'll
be
so
much
easier
for
us
to
implement
enhancements
on
top
of
those,
that's
really
exciting.
So,
as
always,
we
welcome
feedback
through
discussion
on
the
issues
that
we
mentioned,
we'll
link
to
them
below.
You
can
always
email
me
at
jheimbook
gitlab.com
about
these
or
other
issues.
In
our
testing
background,
thanks.