►
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).
B
Yeah,
like
we
were
talking
about
how
to
have
to
track
test
cases
right,
I
didn't
like
test
results
per
se.
We
do
not
have
a
test
case
management
system
yet,
but
with
the
effort
to
da
food
everything
in
good
laughs,
we
have,
let
me
just
pull
up
and
a
project,
so
we're
just
gonna
reuse,
what
we
have
and
iterate
on
it,
adding
new
features
to
it.
Quality
engineering
department,
nezam,
has
a
project
with
a
list
of
issues,
and
let
me
pull
that
up
right
now.
B
You
see
my
screen,
sir
yep,
so
we
have
a
prototype,
what
people
type
where
we
create
issues
which
are
essentially
test
cases
and
what
we
want
to
see
in
the
end
is
essentially
these
are
the
little
tests
and
a
pass/fail
flag
per
se.
So
the
idea
here
is
that
you
shouldn't
use
issues
and
labels
like
this
is
a
passing
and
staging
and
passing
in
master
and
I.
Think
I
think
that
we
have
some
of
these
represented
on
the
port.
B
Let
me
see
test
results,
and
so
essentially
we
want
to
see
like
what
are
the
red
and
green
say
this
on
these
tests
and
an
iteration
to
move.
This
is
have
a
CI
job
that
post
results
to
this.
We
only
have
the
building
blocks.
We
have
api's
the
update
issues.
We
have
API
you
to
add
comments
or
add
labels
or
whatnot.
In
the
CI
pipeline
we
could
output
an
artifact,
a
list
of
test
cases.
B
What
I
was
run
right
and
what,
if
to
number
it
maps
to
in
this
project,
in
the
testis
project
and
towards
the
end
of
the
pipeline,
there's
a
specific
CI
job
that
reports
the
list
of
results.
So
test
case
map,
to
which
issue
number
and
then
it
will
make
an
API
call
to
update
either
pass
or
fail
status
in
this
project
and,
as
things
run,
the
issue
board
is
essentially
your
test
results.
Sorry,
what
is
failing?
B
What
is
passing
and
that's
that's
one
way
to
to
track
test
results
and
have
an
audit
trail
or
what's
most
be
month
or
in
the
end,
like,
for
example,
like
create
a
motion
because
has
case.
If
you
look
at
the
like
the
comments
section
right,
it
would
just
be
an
a
an
API
call
from
that
reporter
runner
job
to
say,
create
a
new
mush
request.
Passing
on
staging
ran
today,
tomorrow
create
new
modulus
path
on
staging
and
etc.
B
I
mean
we
can
even
track
multi-dimensional
test
results,
meaning
it
could
be
passing
in
master
but
failing
on
staging
and
then,
but
the
result
is
tracked
in
one
single
place
and
there's
an
audit
trail
and
I'd
love,
and
this
reuses
his
lab
project
issues,
CI
Runner
and
also
our
API,
to
update
this,
and
that's
the
general
idea
that
that
self
and
I
have
been
discussing
about.
So
what
do
you
think
Zeff
yeah.
A
B
B
Let
me
stop
sharing
my
screen,
so
we
can
see
each
other
better.
So
yeah,
like
it's
just
half
of
the
runner
and
sorry
there's
a
reporter
not
running
the
reporter
CI
job
have
an
option
to
if
tests
not
found
create
a
new
one
and
that's
like
ensuring
that
it's
always
the
latest
and
it's
source
of
truth
test
results.
Yeah.
A
And
if
we've
added
a
new
test
and
don't
have
initiated
yeah
I'm
thinking
too,
when
we
we're
gonna
have
all
of
it,
we
already
have
the
j-unit
files
that
we
could
use
to
actually
read
a
lot
of
this
information.
Exactly.
B
Extend
from
that
right
sure,
let's,
let's
just
the
artifact,
could
be
from
the
j-unit
report,
like
the
list
of
tests
in
the
JD
report
powers
this
additional
step
to
like
update
the
project
entities
so
new
thing,
the
the
get
lab
building
blocks
per
se,
let's
just
make
it
suit
our
needs
with
what
we
have
and
makes
next
step
is
iterate
like
get
all
our
stakeholders,
product
managers
and
and
designers
who
hey?
How
can
we
turn
this
into
the
next
generation
thing?
If
you
have
looked
at
our
history
issues?
B
That
much
because
are
very
similar
to
share
very,
very
similar
things
right
test
cases
could
also
be
an
extension
of
issues.
It's
it's
the
same
building
blocks,
inheriting
from
the
same
for
lack
of
a
better
term
base
class
per
se,
and
that's
how
we
have
been
building
things.
I
think
it's
aligns
with
the
same
pattern
of
iteration.
A
Yeah
I
would
agree,
and
with
our
framework
right
now,
we
could
actually
we
could
tag
each
individual
test
with
its
issue
or
epic
number
itself
and
use
that
in
the
in
the
j-unit
files
to
just
automatically
find
what
we're
looking
for,
and
we
maybe
can
even
figure
out
some
other
automation,
because
if
we
have
a
tag
then
we
can.
We
can
target
those
tests
within
our
runs
right
right
and
we
can
even
have.
B
Stage
and
group
labels
who
own
CSS,
so
if
it
fails,
it
notifies
that
team
in
the
rescue
in
the
issue
and
then
like
the
audit
trail,
is
there
right,
like
you,
can
even
go
back
in
Cal?
Hey
I
mean
it's
comments,
but
hey
iteration
is
better
than
having
nothing.
But
you
look
for
the
comments
Oh
like
this
during
this
week.
This
has
failed
five
times.
B
Why
and
we
have,
we
have
a
trail
on
that
I
would
say
the
emphasis
should
be
not
ethics.
Let
me
be
clear
projects
and
shoes,
so
the
artifact
that
feeds
to
the
API
that
calls
to
the
reporting
in
chasm
is
what
is
the
URL
path
to
that
project
and
the
issue
number,
and
if
this
is
like
test
case
sorry
test
rails
has
Kay's
ID
exactly
the
same
thing
like
when
they
have
a
Jenkins
reporter
every
point:
it's
that's
real.
What
we
need
is
it's
a
test
session
ID
we're
using
this
as
like.
B
A
B
B
Again,
very,
very
crude,
but
so
like
I
want
to
know
what
what's
passing
in
master.
It
was
passing
in
staging
and
this
this
these
two
can
recite
together.
Like
you
see
this,
this
one,
this
was
this
test
is
passing
and
stating,
and
also
this
test
is
also
passing
in
master
yeah.
I
love
our
reshoot
boards,
with
with
a
new,
exciting
and
things
it.
It's
very
cool.
B
B
Anything
else
stuff
you
want
to
you
want
to
add
to
this.
We
should
probably
do
some
free,
fighting
I
think
it's
something
that,
as
a
cold
the
engineering
department,
we
have
to
provide
to
our
stakeholders
and
then
make
it
highly
visible
that
hey
these
are
the
tests
that
are
running
and
it
has
an
audit
trail,
but
any
dots.