►
From YouTube: Enterprise features test gap plannng
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
So,
oh
sure,
my
screen,
here's
our
show
you.
What
I?
Can
you
see
my
screen?
Yes,
I
can
yeah.
So
this
is
first
draft
of
a
test
plan
test
coverage
plan
for
the
enterprise
features
on
the
planned
stage,
so
I
have
separated
and
by
the
time
tier
or
plan
with
gold
in
the
top
and
then
bronze
in
the
bottom.
A
A
I
do
believe
in
a
test
environment,
I,
think
having
unit
integration
and
we're
doing
a
good
job
of
that
here
in
get
lab,
but
there's
value
in
retesting
the
whole
flow
at
the
top,
making
sure
that
the
functionality
works
right.
So
it's
it
can
be
seen
it's
more
like
a
scenario
flow
and
not
just
like
work,
fine
NMR's
created.
A
It
should
be
more
map
to
the
use
case
because
we
in
the
end,
we
do
want
to
show
this
to
to
our
customers
by
then
and
wonder
test
case
things
at
the
end
to
describe
the
scenario
that
enterprise
customer
is
using
because
the
backend
and
unit
tests,
the
test
report,
will
not
make
sense
at
the
business
layer
because
it
doesn't
map
to
a
business
use
case.
So
we
should
structure
the
scenario
based
test:
let's
call
it
that
or
the
enjoyment
has
to
be
more
business
facing
yeah.
B
Yeah
I
am
I
completely
agree
with
you
unit
testing.
They
are
for
developers,
but
if
we
want
to
but
I
think
it's
important
to
have
tests
for
the
the
whole
flow
and-
and
we
can
even
think
about
like
having
kind
of
our
smoke
tests
in
a
way
that
do
everything
complete
flow
from
I.
Don't
know
the
creation
of
a
project
until
and
then
issue
is
created,
and
then
this
issue
is
turned
into
an
M
R
that
is
reviewed
and
then
merged
back
and
then
CI
is
executed.
We
could
have
things
like
that.
B
You
know
more,
like
I,
don't
know
if
it
could
be
on
smoke,
testing
or
some
other
Pro
shown
in
testing,
but
yeah,
and
let's
imagine
that
here
in
the
unit
we'll
have
like.
Probably
thousands
of
tests
in
here
we
would
have
here-
would
have
not
that
much
problem
because
of
the
time
that
they
take
to
execute,
probably
better
to
focus
in
the
beginning.
In
the
happy
path
scenarios
for
the
entrance.
A
A
Relying
the
in
the
other
layers
for
for
alternatives
and
educates
I
think
that's
great
call-out
I
think
it
should
be
critical,
happy
path.
Cases
need
to
go
through,
I've
done
all
the
edge
cases.
We
move
it
down
to
the
lower
layer.
That's
that's
probably
the
best
kind
of
action
here.
What
is
what
is
your?
A
What
are
your
thoughts
on
how
we
can
track
this
in
the
test
case
project
that
we
have?
Is
we
see
this
as
the
the
Rupp
plan
and
then,
when
it's
identified,
we
go
and
create
issues
in
the
test
case
project
with
like
gold
silver
labels.
So
we
know
that
this
is
need
to
be
assigned
to
somebody
and
and
done
like.
Do
you
see
this
being
used
throughout
the
whole
effort
or
just
as
we
identify
gaps.