►
From YouTube: Verify:Testing 14.6 Milestone Refinement Kickoff
Description
Walkthrough of the 14.6 planning issue: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/72
The big focus will be on resolving performance issues of slow build artifact endpoints previously identified.
A
Hey
I
wanted
to
walk
through
the
14-6
planning
issues.
We
kick
off
refinement
actually
a
couple
of
days
into
refinement
already,
so
I'm
a
little
behind
on
this,
so
14.6
you'll
be
fully
in
the
hands
of
the
new
product
manager
at
that
point.
But
what
we
have
as
a
theme
is
we're
really
continuing
to
focus
on
getting
posted
first
towards
that
and
working
towards
that
we're
going
to
be
focused
on
several
of
the
performance
issues
that
we
uncovered
as
we
dug
into
especially
build
artifact
related
endpoints.
A
So
we
have
a
number
of
those
on
the
board
that
are
going
to
be
tagged
with
the
performance
label,
so
it
should
be
pretty
easy
to
find.
They're
called
that
as
too
slow.
One
of
our
q4
okrs
is
identifying
in
points
where
we
can
change.
Our
objects
defaults
back
closer
to
one
second,
from
the
find
second
new
default,
so
that
we
can
continue
to
deliver
just
outstanding
performance
for
customers,
especially
around
build
artifacts
performance.
A
A
This
is
really
just
replicating
what
we
have
on
the
test
coverage
project
summary
view
today,
but
it
is
our
first
step
towards
this
nbc
and
we
believe
that
this
kind
of
top-down
view,
for
not
just
the
director
personas
but
also
for
the
the
team
lead
persona,
is
going
to
drive
additional
pipelines
being
run
that
upload
those
files,
those
files
being
junit,
xml
and
covertura
xml
files
that
drive
test
results
and
coverage
data
towards
that.
We
need
to
be
able
to
track
those
things.
A
So
we
have
usage
ping
in
here
for
upload
of
artifact
report,
corbatura
artifact
report
junit.
That
will
in
turn
drive
our
kind
of
team
kpis,
and
then
we
also
have
that
test
coverage
data
and
then
the
last
one
I'm
going
to
call
out.
This
is
one
that
we've
kind
of
moved
along
a
couple
of
times
is:
we've
had
to
push
more
things
out
related
to
build
artifacts,
but
it's
implementing
that
sax
parser
for
cobratura.
A
That
should,
in
turn,
help
us
up
the
limit
on
those
curvature
files
as
well
coverage
reports
as
well,
which
again
will
increase
overall
usage
of
that
feature,
and
once
we
have
tracking
on
it,
we
can
see
what
the
impact
is
there.
So
I'm
really
excited
to
see
those
two
go
out
in
tandem,
see
what
that
lift
is
as
we
implement
those
those
features.
I
believe
the
genie
is
going
to
be
working
on
some
research.
A
We
don't
have
anything
in
the
milestone
yet
and
I
will
fill
in
as
we
get
our
q4
okrs
set
alignment
with
those
so
that
we
as
a
team,
know
we're
working
towards.
So
if
you
can
start
to
take
a
look,
we
have
a
good
number
of
things
in
here
that
are
back-end
and
front-end
that
can
be
reviewed,
refined
or,
and
then
a
weight
applied
to
them.
Once
you
have
a
weight
on
it,
go
ahead
and
move
it
on
over
into
ready
for
development.
Thanks
team
cheers.