►
From YouTube: GitLab 14.6 Kickoff - Verify:Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
Issues Discussed:
https://gitlab.com/gitlab-org/gitlab/-/issues/342536
https://gitlab.com/gitlab-org/gitlab/-/issues/337650
https://gitlab.com/gitlab-org/gitlab/-/issues/33418
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
heibeck,
the
product
manager
for
the
testing
group
and
the
verify
stage
at
gitlab
today
I'll
be
previewing
the
work
the
team
is
doing
with
the
for
the
upcoming
14-6
milestone
you'll,
find
a
link
to
the
14-6
kickoff
page
and
to
these
items
and
verify
stage
direction
page
with
discussion
of
our
future
work.
In
the
comments
below
the
video,
you
can
always
reach
me
at
jheimbach,
gitlab.com
or
through
comments
with
the
group
testing
label
on
issues
with
the
group
testing
label
in
the
larger
gitlab
project.
A
I'm
already
sharing
my
screen,
showing
our
planning
issue
for
14
6.
in
the
14-6
milestone.
The
team
is
continuing
to
focus
on
performance
issues
as
part
of
our
product.
Investment
theme
in
gitlab
hosted
first,
specifically
we're
looking
to
address
several
build
artifact
related
endpoints
that
are
too
slow
that
we
found
as
part
of
our
latest
slo
review.
A
A
couple
of
those
issues
that
I
want
to
highlight,
one
of
them
is
a
bug
around
june
unit
parsing
is
failing
when
a
large
number
of
files
are
uploaded.
So
if
you
have
decomposed
your
test,
suite
across
many
many
different
test
suites
and
are
trying
to
upload
a
lot
of
junit
xml
at
once,
the
endpoint
can't
handle
it.
A
So
part
of
that
is
related
to
test
report.
Endpoint
is
often
too
slow.
We
think
that
we
can
solve
for
both
of
these
at
the
same
time
or
solving
one
of
them
will
solve
the
other,
and
we've
previously
talked
about
the
sax
parser
for
coverterra
on
other
kickoffs.
We've
had
to
push
that
work
back
due
to
other
higher
priority
issues,
but
it
is
an
area
where
we
want
to
dig
in
in
this
milestone
so
that
we
can
handle
those
larger
cobra
tour
reports
that
we've
talked
about
previously.
A
I
also
want
to
highlight
the
work
the
team
is
starting
on
the
project.
Quality
summary
nbc
gina-
and
I
have
talked
about
this
a
couple
of
times
on
our
kickoff
calls
we're
excited
that
the
team
is
starting
on
creating
the
empty
page,
so
we'll
be
able
to
navigate
to
it.
Adding
our
test
coverage
data
point,
which
we
already
have
another
view
for,
but
also
being
able
to
introduce
other
features
that
we're
going
to
highlight
later.
A
We
think
that
as
users,
especially
that
executive
persona
get
to
this
page,
they'll
be
able
to
see
other
features
that
we
have.
We
know
that
awareness
is
a
problem,
especially
around
uploading
test
report
data.
We
know
that
customers
run
tests,
but
you
may
not
know
that
you
can
see
a
better
detailed
view
of
that
test
outside
of
the
job
log
just
by
uploading
the
artifacts
already
created.
A
So
those
are
a
couple
of
the
problems
in
the
areas
that
we're
going
to
dig
into
and
14
6.,
and
I
also
want
to
introduce
the
new
product
manager
for
testing
robbie
who's
going
to
be
hosting
this
call
going
forward
robbie.
Would
you
introduce
yourself
and
then
we'll
hand
it
off
to
gina
to
talk
about
the
research
and
design
work?
That's
happening
in
this
milestone.
B
Hi
everyone-
this
is
robbie,
I'm
looking
forward
to
meeting
everyone
and
picking
up
the
testing
product
suite
to
mature
it
and
continue
to
build
out
features
that
are
valuable
to
you.
My
background
is
in
software
engineering
and
we're
also
working
as
a
solutions
architect,
helping
customers
use
gitlab
enterprise
at
scale,
so
I'm
excited
to
be
coming
internally
and
continuing
the
work
with
gitlab
and
I'll
hand
it
over
to
gina.
Now.
C
C
the
next
one
is
around
project
quality
summary
which
james
hinted
at
earlier.
We've
noticed
that
there's
some
gaps
in
that
mvc
design.
So
we
wanted
to
kind
of
clear
those
up
with
this
issue
and
some
other
issues,
but
this
one's
specifically
about
adding
an
empty
state
where
we'll
focus
on
providing
different,
empty
states
for
specific
scenarios.
C
Finally,
this
last
issue
that
we're
bringing
in
is
an
area
where
we
see
a
good
amount
of
gaps
in
the
current
experience
today
around
artifacts,
and
it's
something
that
we
wanted
this
issue
something
we
wanted
to
do
in
previous
releases
as
it
provides
some
more
meaningful
data
around
artifacts.
That
would
be
important
to
take
into
consideration
when
taking
an
action
upon
them
like
deleting
them.
A
Thanks
gina,
I'm
really
excited
about
those
kind
of
we've,
called
it
empty
state
of
showing
all
the
possible
features,
and
even
if
we're
not
going
to
be
able
to
introduce
those
to
that
project,
quality
summary
calling
out
what
they
are
to
help
drive
awareness
top
down
from
those
personas
and
gain
valuable
insights
for
the
teams
and
great
work
on
that
design.
It's
some
of
the
best
design
work,
I've
seen
kudos
and
also,
as
always,
we
welcome
feedback
through
a
discussion
on
these
issues.