►
From YouTube: GitLab 14.4 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/333442
https://gitlab.com/gitlab-org/gitlab/-/issues/337650
https://gitlab.com/gitlab-org/gitlab/-/issues/338946
A
Hi,
I'm
james
hembach,
the
product
manager
for
the
testing
group
in
the
verify
stage,
gitlab
and
today
I'll
be
previewing.
Some
of
the
work,
the
team's
going
to
be
doing
in
the
upcoming
14-4
milestone
you'll,
find
a
link
to
the
14-4
kickoff
page
with
links
to
these
items
and
the
verify
state
direction
page
with
discussion
of
our
future
work.
In
the
comments
below
the
video,
you
can
always
reach
me
at
jhanbook,
gitlab.com
or
through
comments
on
issues
with
the
group
testing
label
in
the
gitlab
project.
A
So
I'm
sorry,
my
screen
already
showing
our
14-4
planning
issue
and
in
this
milestone
the
team
is
going
to
continue
our
focus
on
reliability
and
performance
really
related
to
build
artifacts.
A
One
issue
I
want
to
call
out
is
implementation
of
the
saks
parser
for
the
cobra
terra
reports
and
that's
what
drives
our
test
coverage
visualization
in
addition
to
a
performance
boost
from
changing
this
out,
we're
looking
at
this
new
parser
to
help
us
safely
increase
the
size
limit
of
the
coverture
reports
today.
So,
as
you
know,
we
often
have
reports
that
are
larger
than
that
10
mega
megabyte
size
limit
and
we
just
can't
parse
them
today.
A
They
upload,
but
they
are
not
getting
parsed
and
then
we've
been
keeping
a
close
eye
on
our
error
budget
as
a
team
and
some
of
the
build
artifact
related
functionality
that's
recently
transitioned
over
and
that
we've
taken
ownership
of
isn't
as
performant
as
we'd
like
is
causing
us
to
get
into
the
red
on
our
air
budget.
A
So
in
14
4
we're
going
to
be
reviewing
two
of
those
endpoints
that
are
slower
some
of
our
worst
performers
that
we
found
in
trying
to
get
those
a
little
bit
more
performance
so
that
we're
not
exceeding
our
error
budget.
One
of
them
is
this
test
report
endpoint
and
then
just
listing
out
all
of
the
job
artifacts,
so
we're
hoping
to
get
those
cleaned
up
and
then
in
the
14-4
milestone,
we're
doing
several
pieces
of
research.
A
I'm
working
on
some
better
understanding
of
the
user
journey
in
creation
and
uploading
of
artifacts
being
used
by
testing
features
like
junit.xml
files
and
coveratura
xml
files
and
gina
is
going
to
be
working
on
validating
some
of
our
jobs
to
be
done
for
a
couple
of
our
categories.
So
gina,
can
you
walk
us
through
what
you're
working
on
and
what
we're
hoping
to
learn
in
your
research.
B
So
one
of
the
categories
that
we
are
evaluating
jobs
to
be
done
for
is
usability
testing,
and
that
is
this
first
point
here.
So
I'll
just
jump
over
the
research
issue.
We
have
a
plan
to
move
usability
testing
from
minimal
to
viable
in
july
of
2022.
So
this
research
effort
is
to
prepare
for
that
category.
B
Maturity
scorecard
that
will
run
for
for
usability
testing
to
make
that
move
and
we'll
be
holding
user
interviews
with
internal
git
lab
folks
to
learn
more
about
their
motivations
and
their
goals
and
any
necessary
steps
to
accomplish
an
outcome.
That's
related
to
usability
testing
and
that's
already
begun
and
we're
recruiting
for
that,
and
then
we'll
use
the
insights
that
we
find
to
form
or
validate
jobs
to
be
done,
which
we
only
have
one
for
right
now.
B
The
other
thing
that
is
going
on
in
the
ux
area
of
this
milestone
is
the
project
quality,
summary
iterations,
and
we
have
a
stretch
goal
of
being
able
to
design
the
iterations
of
this
based
on
the
feedback
that
we
received
from
the
solution.
Validation
phase
previously-
and
this
includes
some
various
important
updates
to
the
original
design
that
will
improve
the
overall
experience
and
we're
really
excited
to
push
this
feature
forward
and
to
see
all
the
insights
that
come
out
of
the
research
that
we're
doing
this
milestone.
A
Awesome,
thank
you.
Gina.
I'm
excited
to
see
the
research
and
watch
those
interviews
and
see
how
users
are
using
both
review
apps
and
our
visual
review
tools,
if
at
all
so
that'll
be
fun.
As
always,
we
welcome
feedback
through
discussion
on
these
issues.
This
video
or
you
can
always
email
me
at
jhembook
gitlab.com
about
these
or
other
issues
in
the
testing
backlog.
Thanks.