►
From YouTube: Verify:Testing 13.10 planning issue revisit
Description
Update walking through OKR alignment now that they are close to finalized for the quarter and how they map to work in this milestone for Testing.
Testing 13.10 planning issue: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/34
CEO OKRs: https://about.gitlab.com/company/okrs/fy22-q1/
A
Hey
team:
I
wanted
to
record
an
update
to
the
1310
planning
issue
which
you
can
see
on
my
left.
I
don't
know
where
it's
going
to
show
up
on
youtube,
updated
capacity.
Ricky
provided
some
updates
here.
Do
you
want
to
stress
we're
going
to
try
to
continue
to
leave
some
time
or
some
capacity
in
the
milestone
to
help
the
growth
team
on
a
code,
quality
experiment
which
is
a
great
segue
into
some
of
the
okr
match
up?
That's
what
I
worked
on
today
and
the
update.
A
So
the
first
one
graphing
the
average
code
coverage
of
all
the
groups
projects
for
me
that
maps
into
our
objective
around
a
popular
next-gen
product
key
result:
there
increasing
stages
per
organization
from
x
to
y.
If
you
dig
through
the
issues,
some
of
them
are
confidential.
You
can
see
what
those
actual
numbers
are
a
little
bit
of
explanation
here,
because
it
may
not
be
exactly
clear
that
mapping
for
us
adding
another
premium
tiered
feature
it
continues
that
value
for
the
verify
stage.
A
So
this
is
going
to
encourage
organizations
that
already
have
a
premium
license
to
adopt
verify
if
they
don't
already,
because
there's
additional
value
there
and
specifically
within
verify,
there's
another
integration
that
they
can
hopefully
drop
or
plug
in
for
jenkins
or
external
reporting,
whatever
it
is
that
they're
doing
to
get
that
data
today,
it's
another
thing:
they
don't
have
to
do
and
not
have
to
pay
another
cent
for
it,
so
great
value
there.
A
The
other
two
that
I
was
able
to
map
up
are
the
two
actionable
items
that
we
have
out
of
the
mr
review.
Differentiate
tests
expanded
and
the
de-emphasized
test
results
status,
icons
those
directly
map
into
trying
to
achieve
that
sus
target
of
75.
Both
of
these
are
actionable
items
that
came
out
of
the
mr
review.
A
We
know
that
the
mr
page
is
highly
trafficked
and
so
any
confusion
that
we
can
eliminate
about
that
widget
increases
our
success,
increases
the
sus
and
we're
also
going
to
be
digging
into
in
this
quarter,
trying
to
figure
out
why
more
people
aren't
using
those
unit
test
reports
in
the
test
summary.
So
I
wanted
to
walk
through
that
just
to
give
some
context
to
that
update
I'll
drop,
a
link
to
the
planning
issue
and
this
video
into
slack
channel
here
shortly.