►
From YouTube: Magento MSI Open Demo. November 9, 2018
Description
Agenda:
- General update on release preparation
- Description of the critical bugfix found during the week with different order statuses (Cancellation and Credit Memo in the scope of a single order)
- Reservation flow
- New Readme files and Documentation
- Test Scenarios and test coverage of MSI
A
A
The
first
issue
was
devoted
to
order
cancellation,
where,
at
the
time
of
the
order
cancellation,
we
can
select
all
the
order
item
but
not,
but
we
supposed
to
cancel
just
not
invoiced
part
of
the
order
item
and
looks
like
this
issue
was
brought
as
a
result
of
the
bug
fix
we
made
during
durin
during
the
bug
fixes
before
in
this
cover
the
regression
cycle.
So
it
was
pretty
critical
one,
as
you
can
see
like
placing
an
order
with
ten
items
and
after
that
innovation,
seven
of
them
and
made
a
making
a
cancellation.
A
Actually,
we
created
a
compensation
law
reservation
for
the
who
order
item
so
for
all
the
ten
items
and
that
led
to
to
incur
incorrect
calculation.
So
the
expected
behavior
in
this
case
to
make
a
compensation
compensation
and
the
make
a
cancellation
just
for
just
for
not
invoiced
part.
So
in
this
particular
case
for
three-
and
this
is
that
was
one
issue.
A
Another
issue
was
with
a
partial
credit
memo
and
we
had
pretty
sophisticated
case
when
we
placed
an
order
for
for
ten
items
such
that
we
made
an
invoice
for
seven
sheep,
three
items
and
cancelled
order
afterwards
and
then
creating
the
credit
memo.
We
had
a
problem
and
we
got
the
incorrect
source
quantity.
So
eventually
we
got,
we
got
even
more
than
we
had
before.
This
issue
was
also
fixed
and
the
flower
will
demonstrate
how
it
works
now,
and
these
two
issues
would
be
delivered
today.
A
So
now
we
are
making
quite
a
lot
of
many
old
testing,
along
with
delivery
of
this
issues,
just
to
make
sure
that
fixing
these
issues,
we
are
not
introducing
anything
anything
new,
so
as
a
side
effects.
We
are
not
introducing
additional
bugs
slower,
feel
free
to
share
your
screen
and
demonstrate
what.
How
has
this
issue
been
fixed.
B
B
B
B
B
And
that
let
me
check
our
quantity
now,
after
placing
order
yeah
we
have.
After
previous,
we
have
90
so
after
place
order.
We
have
80
sellable
quantity,
so
what
I
do
I
will
do
just
with
one
product,
because
in
this
ticket
see
is
written
about
two
of
them,
but
it's
not
really
matter
so.
I.
Do
partial
invoice,
for
example,
for
seven
items.
B
B
B
C
B
B
B
B
A
Just
to
provide
a
little
bit
more
info,
so
we
found
this
while
we
were
testing
our
previous
fix
and
the
previous
bar
demonstrated
by
swallow
actually
was
was
led
us
to
the
same
to
the
same
issue.
So
when
we
have
the
like
conciliation,
partial
cancellation
and
after
that,
we
have
the
cricket
memo,
the
order
status
does
not
does
not
count
to
the
final
state
like
like
closed,
because
here
we
expect
that
after
part
of
the
order
would
be
canceled
it
and
all
the
rest
would
be
would
be
refunded.
A
The
order
should
should
come
into
the
into
the
closed
state,
but
currently
it's
still
in
process
the
state,
and
we
we
saw
that
we
introduced
this
issue
from
the
maasai
side
and
we
spent
quite
a
lot
of
time
on
the
looking
the
root
cause
of
the
issue.
After
that,
we
realized
that
actually
the
current
issue
in
magenta.
Now
we
raise
this
issue
and
provided
two
guys
who
are
preparing
to
the
three
preparation,
probably
should
be
trashed
the
issues
not
so
yeah.
A
A
We
should
like
make
the
in
this
particular
case.
Order
does
not
come
to
the
to
the
final
state
and
you
can
cancel
it,
but
this
still
would
be
cancelled
but
not
closed
as
probably
it
is
a
desirable
state
of
the
order
and
in
MSI's
decent
reuse,
even
big
side
effects
and
currently
in
magenta,
because
on
from
the
msi
side,
we
don't
affect
the
order
statuses
in
any
way,
because
order.
Starters
are
now
calculated
based
on
the
order
item
and
we
are
not
effecting
order
item
at
all.
A
This
way
it
was
little
quite
surprising
for
us,
but
why
is
the
side
effects
for
a
messiah's
bigger
than
for
for
magenta
this
autumn
aside,
because
at
the
time
of
the
shipment
we
making
the
sort
deduction,
so
as
flower
demonstrated
to
you,
this
shipment
is
still
available
after
the
last
step.
After
the
the
credit
memo
for
the
who
invoice
part
is
created
so,
but
with
you
can
make
a
shipment,
so
it
is
probably
not
so
critical
for
magenta
is
autumn
aside,
because
all
the
stock
stock
deduction
happens
at
the
time
of
the
order.
A
A
This
is
drastically
changed
when
msi
appeared
and
because,
when
msi
appeared
and
when
MSI
is
up
and
running,
which
magenta
to
the
tree
that
oh
we're
on
the
source
selection
algorithm,
we
deduct
what
we
actually
choose
the
sources
which
should
be
deducted,
and
we
make
this
deduction
so
currently
because
of
the
order
is
not
get
to
Z
to
the
final
status.
We
can
we
can
get
the
incorrect
computation
in
incorrect
calculation
of
the
quantity,
so
this
is
actually
an
issue
we
discovered
today
just.
B
Made
it
that
I
have
instance,
with
magenta
2.3
from
October
an
extra
bed
in
beginning
guy
I,
checked
on
it,
because
I
didn't
have
idea
that
it's
elves
are
such
serial
sins
and
on
that
instance,
order
get
closet
status.
And
this
way
we
was
looking
for
barking
hours
on
our
side.
Msi
spent
quite
a
lot
of
time,
but
when
we
sync
up
with
bring
you
in
code
and
found
out
that,
actually
it's
on
course
I.
A
A
For
example,
when
you
place
an
order,
you
create
the
initial
reservation
when
you
ship,
even
even
partially
part
of
this
order,
we
create
the
compensation
reservation
for
correct,
like
general
calculation
of
the
quantity,
and
we
had
in
a
case
of
partial
cancellation
and
in
case
of
partial
credit
memo.
We
had
a
way
we
had
cases
when
the
computational
reservation
being
created
twice,
and
actually
this
affected
the
whole
computation.
A
A
Probably
that's
all
regarding
the
bug
fixes
and
now
Laurie
will
share,
really
cool
update
for
you
and
because
we
we
want
to
make
a
live
stream
on
November
16,
and
we
want
to
invite
all
of
you.
Laurie
will
shed
more
light
regarding
all
this
stuff
and
what
was
it
going
to
be
so
Laurie
feel
free
to
share
your
screen
and
demonstrate
or
I
don't
know.
Oh
no.
C
I
just
got
some
stuff
to
chat
on
and
I'm
also
going
to
be
posting
all
of
this.
In
the
slack
channel,
we're
going
to
have
a
series
of
blog
posts
coming
out.
Lots
of
tweets
have
already
started.
The
live
stream
is
going
to
be
completely
msi
and
we're
going
to
have
a
wide
range
of
folks
that
are
going
to
be
presenting,
including
bartek
from
bold
he's,
going
to
be
talking
about
the
first
magenta
2.3
plus
msi
project
ricardo.
C
The
rich
he's
also
going
to
be
talking
about
all
the
technical
challenges
that
he
came
up
against
and
architecture,
and
what
it's
been
like
to
work
through
this,
but
then
just
as
going
to
talk
about
b2b
plus
MSI,
a
lot
of
work
going
on
there.
We're
hoping
to
also
have
an
MST
talk
about
some
of
their
experiences.
C
Writing
the
advanced
MSI
extension
and
maybe
a
bit
more
we'll
find
out
from
there
I'll
be
walking
through
some
of
the
documentation
you've
all
been
seeing,
but
it
may
be
news
to
others
as
well
as
dev
docks
and
the
user
guides,
as
well
as
the
wiki,
which
will
like
I
mentioned
last
week,
continue
along
as
we
go
through
milestone,
3
and
Mark
Britain's
also
going
to
be
talking
about
the
future
milestone
3.
We
may
have
some
special
guests
talking
about
some
order
management.
C
It
may
be
crazy,
but
it's
definitely
going
to
be
jam-packed
with
a
lot
of
them
so
for
times
dates.
Links
I,
just
posted
those
to
the
slack
Channel
you're
gonna
see
a
lot
of
tweets
coming
out.
A
lot
of
excitement.
I
know
everyone
over
here
is
really
interested
to
see
what
we're
going
to
be
talking
about
and
all
the
demos.
A
A
We
are
working
pretty
hard
on
me.
Can
our
documentation
better?
So
in
a
latest
update,
we
updated
all
the
readme
files
in
our
modules.
So
now
you
can
easily
read
that
main
destiny
of
each
of
the
module,
and
you
can
see
you
can
see
the
reference
to
the
dev
dogs,
where
you
can
read
more
about
the
universe,
new
inventor
infrastructure
in
general.
A
A
Dismantle
this
monolithic
modulus
on
many
singular
responsible
modules,
and
currently
this
is
MSI
zone
the
project
where
you
can
see
these
ideas
beyond
implemented
and
represented
in
code.
So
all
the
modules
now
contain
this
fancy,
fancy
readme,
which
which
describe
pretty
pretty
good
and
provide
pretty
good
understanding
of
what
the
main
responsibility
of
particular
model.
A
D
D
So
we
have
currently
a
hip
test
is
slightly
out
of
data.
I
need
to
actually
get
it
updated,
but
we
have
a
hundred
and
forty-three
actual
tests
that
will
be
introduction
now
I'm
working
on
one
additional
I'm
working
on
one
additional
test
to
actually
get
that
it's
my
final
PR
that
I
have
open,
so
we
should
have
about
145
tests
when
I
am
when
everything
is
all
said
and
done.
Hopefully,
by
the
end
of
today.
D
Let's
see
what
else
in
the
CV
Raina
build
last
night
to
see
what
the
actual
status
is.
Everything
was
with
extensions,
be
our
show.
We
are
seeing
success
in
the
actual
seee
area,
but
right
now
we're
also
showing
success
in
B
to
B,
but
EE
is
having
one
issue
that
we're
still
looking
into.
There
appears
to
be
a
core
functional
test.
That's
giving
us
a
little
bit
of
an
issue
right
now.
I
have
a
brand
new,
build
running
with
regular
two
three
develop
that
I'll
be
cross-referencing.
D
D
D
It's
just
getting
all
of
everything
synched
up
trying
to
get
all
of
our
PRS
actually
closed
out,
trying
to
get
all
the
notes
and
information
moved
over
to
Tom
so
that
he
can
pick
up
and
start
this
project
on
Monday,
that's
kind
of
the
gist
of
what
I
have
for
you
all
today
and
it's
been
a
pleasure
working
on
this
project.
I'll
definitely
be
here
for
any
troubleshooting
assistance.
That
Tom
needs
for
me,
of
course,
to
troubleshooting
with
him.
Ftf
Jim
general
issues,
but
I'll
be
moving
on
to
whatever
project
I
can
assign
to
you.
E
E
Everybody,
as
John
mentioned
Tom,
will
be
taking
over
all
things
quality
on
MSI
starting
next
week.
He
actually
started
transitioning
already,
but
you
would.
You
will
be
hearing
these
updates
and
you
should
expect
him
to
own
the
quality
of
them
as
high
starting
next
week
and
yeah.
This
is
this
fantastic,
we'll
be
seeing
the
status
of
our
functional
tests
and
having
updates
on
coverage
very
regularly
starting
next
week.
Tom.
Do
you
want
to
add
something
to
what
John
said?
Yes,
let.
F
Me
go
ahead
and
just
give
a
quick
update
on
I,
like
you
said,
I've
sort
of
started
in
this
week
officially
taking
over
on
Monday,
so
give
you
an
idea
where
we're
going
with
this
and
keep
everyone
updated
and
hopefully
get
a
little
from
everyone
to
come
on
board
with
testing.
So,
first
of
all,
big.
Thank
you
to
John.
Absolutely
fantastic.
He's
got
us
help
discuss
here
with
the
automation
from
milestone
to
I
think
he
was
big
part
of
that
success
and
everyone's
very
grateful
for
it.
F
I'm
sure
we'll
still
see
Orion,
but
for
now
on
point
of
contact
for
all
things.
Testing
is
me.
If
questions
are
concerned,
please
feel
free
to
come
to
me
directly
and
I'll
work
through
with
you
on
those
in
terms
of
what
we're
gonna
do
going
forward,
then
so
immediate
concerns
or
immediate
wins
we
can
take
out
of
this
is
certainly
things
like
the
bug
Slava
showed
in
1881.
We
want
to
go
ahead
and
see
where
we
have
critical
bugs.
We
want
to
get
coverage
in
for
those
immediately.
F
That's
something
we
want
to
go
ahead
with
in
terms
of
getting
quality
to
better
point
quickly.
We
currently
have
18
skip
tests
and
nine
of
those
have
bugs
I'm
gonna
follow
up
on.
None
of
those
look
like
they
need
a
little
investigation
to
see.
Are
they
still
current
and
valid
and
if
not
want
to
flip
those
over
and
in
the
bigger
picture,
we
really
want
to
look
at
requirements
coverage.
So
that's
an
exercise.
I'll
go
through
Slava
I'm,
probably
with
mark
as
well
around.
Have
we
defined
the
correct
a
scope?
F
Have
we
got
really
a
cohesive
list
of
what
we
want
to
do,
reprioritize
where
we
need
to
and
that,
and
certainly
a
long
category,
our
catalog
and
cart
and
make
sure
we
have
our
critical
coverage
done
and
then
time
permitting
there's
some
testability
work.
We
can
go
back
into
there's
a
little
tack
there
as
MF
TF.
As
of
all,
we've
got
some
better
functionality
around
moving
things
from
selenium
actions
to
CLI
actions.
There's
winds
they're,
both
instability,
which
we
all
want
with
our
PRS
and
some
performance
gains
as
well.
So
that's
testing
set
of
things.
F
What
I'll
be
looking
at
going
forward?
Also,
one
of
the
key
pillars
of
this
and
you'll
see
a
lot
of
me
because
of
this
is
we
want
to
do
a
bigger
push?
I
personally
want
to
do
a
bigger
push
in
engaging
the
community
with
automated
tests,
getting
their
help
getting
their
understanding
and
selling
this
to
the
community
in
terms
of
this
is
a
great
thing
to
do.
It
has
a
lot
of
value.
F
It's
going
to
help
your
development
and
MSI
stability,
so
I'll
be
coming
out
with
ideas
and
events
around
how
we
get
that
involvement
again,
I'm
primary
point
of
contact
for
that.
So,
if
there's
concerns
within
MSI
with
the
community
started
with
testing
wire
tests,
looking
at
this,
where,
as
reporting
all
can
come
through
me,
but
for
now
you'll
hear
more
for
me
next
week,.
E
The
next
time
I
appreciate
it
and
dear
community
welcome
Tom.
You
will
be
hearing
more
from
him
pretty
soon
and
feel
free
to
reach
out
to
him
regarding
all
questions,
quality
and
all
questions
and
RTF
and
just
any
general
stuff
here,
I,
don't
know.
Igor
I
think
we
can
pass
the
word
over
to
you
if
you
want
to
make
any
other.
E
Announcements
or
past
award
over
to
anybody
else
before
I
forget
I
have
raised
this.
The
issue
that
you
were
referencing
in
magenta
to
302
the
release
team
they've
acknowledged
that
they're
working
on
triaging
it
right
now,
so
we'll
be
hearing
more
on
it
a
little
later,
hopefully
within
an
hour
or
two,
and
that
would
I
think
define
of
the
kind
of
the
destiny
of
two
point
3.0
rtm
today,
if
that's
at
all
happening
because
I
know
we
have
some
dependencies
on
VDS
and
stuff.
So.
A
Cool,
so
probably
probably
that's
all
for
today,
I
don't
have
any
a
lot
of
Arthur
updates,
I,
just
probably
one
more
update.
They
see
that
Lee's
on
the
call
and
the
small
updates
for
you.
We
had
the
internal
internal
communication
devoted
regarding
the
topic
we
discussed
with
you
some
time
ago
regarding
the
possibility
to
deliver
bugfixes
and
calm,
and
we
agreed
internally
that
we
will
provide
the
opportunities
as
a
possibility
to
our
partners.