►
From YouTube: Code Testing and Coverage JTBD Brainstorming 2020-08-24
Description
Brainstorming session for JTBD for the Code Testing and Coverage category.
Issue for JTBD: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/19
Testing JTBD page: https://about.gitlab.com/handbook/engineering/development/ci-cd/verify/testing/JTBD/
A
A
category
is
moving
or
scheduled
to
move
from
minimal
to
viable
at
the
end
of
october,
and
so
as
part
of
that
process,
we'll
be
brainstorming
the
jobs
which
will
later
be
voted
on
and
then
surveyed
out
into
the
customer
base
to
validate.
We
have
the
right
jobs
to
measure
against
as
part
of
the
category
maturity
scorecard
process.
So
I'm
going
to
open
it
up
to
the
team,
I'm
going
to
share
my
screen
and
look
at
the
existing
jobs
to
be
done
on
our
jobs
to
be
done.
Page.
A
A
B
A
A
So
if
there
are
other
jobs
that
are
not
listed
here,
this
is
the
this
is
the
avenue
that
we
have
to
populate
those,
even
if
we
don't
have
a
feature
set
for
it.
If
we
think
that
a
minimally
or
viably
mature
product
would
do
these
things,
let's
get
them
listed
selfishly.
This
also
helps
identify
gaps
in
our
feature
set
that
we
need
to
go
out
and
work
on
implement
so
that
we
can
reach
that
maturity
level
and
continue
to
drive
usage.
C
A
B
A
A
D
A
A
We
just
think
about
it,
as
there
are
certain
jobs
that
you
need
to
do,
that.
We're
building
features
to
do
that
job
and
that's
how
we're
measuring
again
we're
measuring
maturity
against
the
feature
sets
for
the
different
categories,
the
classic
example
in
all
of
the
products,
books
and
examples,
and
one
pagers
about
this-
is
the
there's
a
milkshake
example
that
kind
of
the
person
who
came
up
with
the
concept
put
out
there
and
it's.
A
Why
were
people
stopping
at
a
fast
food
place
to
buy
a
milkshake
during
their
morning
commute
they
were
trying
to
figure
that
out
and
they
figured
out
that
the
milkshake
was
completing
the
job
of
something
interesting
to
drink.
While
they
were
sitting
in
traffic
filled
them
up
was
delicious,
and
I
don't
there's
some
other
nuance
into
that,
but
it
was
the
milkshake
that
did
the
job,
and
so
they
started
to
you
know,
market
more
in
towards
the
the
job
that
was
needed
to
be
done
and
increased
milkshake
sales.
A
B
A
A
When
I
have
tests
that
are
failing,
I
want
to
identify
them
and
where
they
are
in
the
code
as
easily
as
possible,
so
that
I
can
fix
them
quickly
and
get
back
to
my
code
back
to
getting
my
code
to
production
when
all
my
tests
are
passing.
I
want
to
continue
to
build
and
deploy
my
software
without
interruption,
so
I
can
get
my
code
to
production
safely.
B
C
C
How
kind
of
granular
are
we
supposed
to
go
with
these
because
I
guess
is
kind
of
the
overall?
I
want
to
know
why
my
branch
isn't
passing
so
that
I
can
make
it
past.
I
mean
everybody
that
terribly,
but
you
know
what
I
mean
that
kind
of
that's
really
wishy-washy.
Do
we
want
to
be
more
specific
than
that
and
go
right
into
the
the
actual
features
of
I
want
to
know.
A
With
code
coverage
specifically,
do
you
know
what
I
mean?
I
think,
let's
just
brain
dump
today,
so
stepping
out
of
the
exercise
for
just
a
minute
today
we're
starting
the
brain
dump
and
we
had
a
limited
time.
We
took
some
time
to
set
contacts
on
this,
we'll
take
a
couple
of
more
days
and
iterate
on
these
in
the
issue
or
just
add
to
them
in
the
issue
on
in
our
next
team
meeting
I'll
talk
through
the
process
of
what
next
steps
are
or
what
we're
doing.
A
Why
we're
doing
it
and
the
next
steps
for
the
team
to
participate
and
before
we
set
a
survey
out
to
the
team
of
hey
vote
on
the
top
ones.
We'll
do
some
more
refinement
ourselves
within
the
issue,
so
for
now
it
can
be
as
granular
or
as
expansive
as
you
want
and
we'll
worry
about
edits
later.
Let's
just
get
ideas
down
and
not
limit
ourselves.
B
A
A
A
D
A
I
was
thinking
about,
like
our
maturity.
Level,
for
a
developer
is
probably
a
lot
closer
or
at
viable
than
our
maturity
level
for
a
team
leader
director,
and
so
how
do
we
tease
out
that
when
it
comes
to
one
maturity,
score
now,
I'll?
Add
that
to
the
agenda
for
our
ux
chat
this
week
to
talk
with
nadia
and
if
lori
can
make
it
or
I'll
ping
her
and
we
can
track
yeah
in
sync.
Maybe
in
the
issue
for
the
scorecard.
D
D
I
don't
know,
what's
the
deal
there
but
like
there
must
be
some
caveat
like
if
we
really
feel
that
we're
not
much
sure
for
a
particular
person
that
we're
serving.
I
gotta
assume
that,
like
then,
we're
not
ready
to
be
viable
at
that
particular
in
that
particular
area
of
the
product.
But
I
don't
know
I
might
be
wrong
about
that.
D
A
All
right,
I'm
gonna,
not
stop
you
all
from
continuing
your
brainstorming,
because
I'm
seeing
a
lot
of
great
content
come
out
of
this.
I'm
just
gonna
voice
over
that.
Let's
try
to
set
the
due
date
for
final
editions
to
the
issue
to
the
end
of
the
week,
and
then
we
can
distribute
the
issue
to
the
team
for
voting
at
the
beginning
of
next
week
with
the
idea
that
by
the
end
of
next
week,
we'll
have
our
finalized
list
that
will
go
into
the
survey
that
is
going
out
to
the
broader
community
to
measure.
A
A
A
Taking
silence's
acceptance-
great,
I
will
take
you
know
different
emojis
in
the
issue,
as
not
acceptance
of
that
later
cool.
We
are
already
at
the
end
of
time.
This
has
been
a
great
mini
brainstorming
session.
Already
I'm
seeing
lots
of
good
stuff
in
the
doc.
Thank
you
all
so
much
for
helping
me
with
this.
I
really
appreciate
it.
It's
great
working
with
this
team
and
I
will
take
the
next
steps
I,
by
probably
by
the
end
of
the
day
or
overnight
my
night.