►
From YouTube: Verify:Testing 13.10 Refinement Kickoff
Description
Walkthrough of the 13.10 planning issue: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/34
A
Hey
team:
I
wanted
to
record
a
walkthrough
of
the
current
state
of
the
planning
issue
for
1310,
as
we
start,
async
refinement.
So,
as
we
think
about
this
kind
of
the
theme
of
this
milestone
is
wrapping
up.
Some
work
really
focused
on
code
testing
and
coverage
and
I'll
talk
about
that
in
our
deliverables.
A
So
we're
going
to
leave
a
little
bit
of
capacity
open
for
that,
we'll
take
that
out
of
that
80
feature
capacity,
so
the
top
priority
deliverables
for
us,
like,
I
said,
co-testing
and
coverage,
graphing
average
code
coverage
of
all
projects
in
a
group
that
closes
out
that
epic,
so
that
we
get
that
wrapped
up.
And
then
we
have
some
usability
fixes
for
the
test.
Summary
widget
things
that
were
called
out
as
product
and
engineering
were
looking
holistically
at
the
merge
request,
page
and
all
of
the
widgets
that
are
there.
What
makes
sense?
A
A
A
We
think
that's
the
next
area
to
really
dig
into
so
I
wanted
to
call
out
a
couple
of
the
bugs
that
are
top
priority
to
fix
the
code
quality
issue
with
the
docker
hub
rate
limits
ricky.
I
know
you've
already
been
looking
at
this
and
then
the
current
group
code
coverage
data.
All
projects
not
working
consistently,
there's
a
back
end
and
a
front
end
component.
To
that
the
front
end
component
is
already
weighted,
I
believe,
and
sitting
and
ready
for
dev.
A
The
back
end
component
is
not,
but
that
is
blocking
the
front
end
component.
So
we
need
to
get
both
of
those
weighted
and
looked
at
so
talking
about
feature
maintenance,
we're
targeting
20
of
the
weight
of
the
milestone
being
these
types
of
issues.
These
are
the
four
that
are
already
there
database
cleanup
for
the
ci
test
cases
and
the
other
table.
Refactoring
build
artifact
serialization
a
couple
other
things,
so
I'll
really
lean
on
the
team
to
dig
into
those
order,
those
appropriately
for
what
is
most
important.
A
If
need
be
we'll
take
this
cleanup
out
of
this
20
put
it
into
the
feature
bucket.
It
is
something
that's
important.
We
want
to
make
sure
that
table
stays
performant,
while
the
mbc
of
test
history
is
running
and
then
okay,
our
alignment
still
waiting
on
executive,
okay,
errors
to
get
lined
up.
So
probably
in
alignment
with
you
know:
oh
I'm
blanking
on
it
next
generation
or
lovable
product
and
increasing
active
users.
You
know
all
of
the
usability
stuff
is
gonna
feed
into
that.