►
From YouTube: Magento MSI Open Demo. July 27, 2018
Description
Today’s Agenda:
1. New Documentation written by @Lori Krell
2. MFTF tests coverage for Mass Inventory transfer Tool story and Backorders with negative threshold story by @Ivan Pletnyov
3.Hip Tests scenarios
3. General updates
A
A
So
we
will
show
you
update
today
what
exactly
test
we
were
written
and
what
the
documentation
company
in
our
our
functionality,
which
was
present
because
in
magenta
to
now
it's
very
important
not
just
provide
new
functionality
but
covers
this
functionality
with
different
kind
of
tests,
especially
with
mfk
f1.
So
am
magenta.
Msi
is
a
pioneering
project
which
which
company
all
the
functionality
with
the
new
acceptance
testing
using
you
a
media
framework
and
also
we,
we
document
as
much
as
possible,
all
the
other
functionality
and
the
other
feature
set
provided
by
MSI.
A
So,
let's
follow
the
agenda.
I
described
in
a
Massiah,
Channel
and
now
Laurie
will
describe
you
the
documentation
written
during
this
week's,
covering
both
of
these
stories
and
other
stories
we've
been
talking
as
we
had
a
open
grooming,
so
we
have
quite
a
bunch
of
updates
for
the
documentation.
I
will
stop
sharing
my
screen.
B
Okay,
so,
as
Igor
has
already
discussed
the
documentation
I'm
trying
to
keep
it
in
line
with
all
updates
that
are
occurring
either
in
for
quests
or
in
develop,
so
the
documentation
may
at
times
be
ahead
a
little
bit
with
the
development,
but
it
will
try
to
100%
match
it
as
we
go
through
milestone
2,
you
can
find
content
through
the
wiki
under
the
MSI
user
guide
section.
So
if
you
are
looking
for
that
information,
that's
where
this
is
located
so
for
the
mass
action
tool
updates.
B
This
has
been
overhauled
based
on
last
week's
demo
and
some
updates
and
discussions
we've
started
having
this
week
as
milestone
to
continues
you're
going
to
see
even
more
additions
to
this
page,
especially
for
the
transfer
inventory.
As
that's
being
worked
out,
you
will
notice
this
very
important
section
here.
This
is
due
to
current
front
functionality
in
develop
and
will
update
and
change
as
we
go
through
milestone
2.
That
gives
you
very
important
information
to
understand
how
default
source
and
default
stock
will
work
and
the
guidelines
and
the
sort
of
the
rules
around
it.
B
As
you
work
with
the
mass
actions,
highly
recommend
looking
through
this
information
to
really
best
understand
it
as
before
you
use
these
tools
and
again
these
will
change
as
the
tool
progresses
and
I
tried
to
include
some
screenshots
here.
You'll
see
that
our
anime
to
also
help
our
users
better
find
items
without
cluttering.
This
immensely,
you
can
look
through
this.
B
It
covers
everything
from
mass
assigning
products
to
to
new
sources,
transferring
inventory
to
source
which
includes
the
source
item
status,
as
well
as
the
quantity
in
milestone
to
you,
that's
going
to
expand
and
then
unexciting
product
sources.
If
you
were
part
of
the
demo
last
week,
this
is
going
to
look
very
familiar,
but
we
wanted
to
make
sure
that
everyone
was
very
much
aware
of
this
section
to
help
really
highlight
these
pieces.
I
also
updated
the
getting
started
with
MSI,
which
usually
is
read
right
after
installing
or
upgrading
to
MSI.
B
You
will
notice
that
there's
a
new
section
on
multi
source
merchants
and
understanding
default
source
in
stock
to
give
and
highlight
that
information
as
early
as
possible.
This
information
will
probably
move
into
its
own
section
to
help
single
source
merchants,
expand
their
business
and
move
into
multi-sourcing.
B
So
you
don't
see
a
lot
of
best
practices
start
to
be
added
to
this
and
expand
to
further
add
to
the
documentation.
This
week
this
was
updated
last
week
and
into
this
week
for
all
of
the
back
orders
and
the
new
updates
for
the
negative
out
of
stock
threshold.
It
gives
extensive
examples,
including
some
screenshots,
to
really
help
provide
examples
and
what
you
should
expect
to
see
as
you
work
through
this.
The
the
features
and
the
new
updates
and
this
information,
as
it's
being
updated,
will
also
be
updated
in
the
global
and
product
settings.
B
So
you'll
see
updates
to
this
table
as
well
as
we
go
through
milestone
2,
as
some
of
these
features
may
change,
either
from
source
or
stock
or
will
have
you
far
more
defined
information.
So
you
really
know
what's
going
on
under
the
covers,
and
finally,
this
week
I
started
updating
some
of
the
shipment
in
order
information.
It's
just
a
cleanup.
It
doesn't
have
any
changes
to
current
functionality,
but
in
case
you
needed
to
show
some
of
the
sympho
to
others,
or
you
wanted
to
look
through
it.
B
A
Thank
you
Laurie.
Now
you
guys
see
how
magenta
seriously
treat
the
documentation
process
and
that
knew
all
the
new
lead
piece
of
software.
Added
to
the
codebase,
now
documented
documented
pretty
clean
with
really
good
gif
animations.
So
you
can
see
you
can
see
it
all
this
new
documentation
on
MSI
wiki
page.
So
now,
let's,
let's
go
to
another
analysis
item
in
our
agenda
and
one
click
no
will
launch
the
MHD
f-test
for
cover
and
as
a
functionality
of
mass
inventory
migration
tool
and
negative
the
quarter
threshold.
So
it
won't
feel
free
to
share
your
screen.
A
So
in
this
cup
of
this
test
we
already
made
one
assertion
and
we
check
that
with
a
negative
stress,
hold
it's
not
possible
to
buy
more
quantities
than
naturally
and
then
the
amount
of
the
saleable
quantity,
because
before
that,
the
recorder
functionality
actually
meant
that
the
number
of
product
available
is
just
infinite,
with
the
negative
stress
hold
the
mess,
all
the
quantities
tinted
and
one,
and
actually
the
check
assertion
to
buy
more
product,
which
is
available.
The
negative
cancel.
B
A
A
A
A
A
B
C
A
So
in
this
cup
of
this
test
we
will
demonstrate
that
we
will
select
products
on
a
product
grid
and
we
will
unassign
products
for
specified
sources
and
after
that,
the
MSL
functionality
will
drop
the
relationship
between
product
and
particular
source
and
actually
drop
the
number
of
quantities.
So
we
will
literally
remove
existing
source
items.
A
It
takes
some
time
because
each
MFT
f-test
should
prepare
an
environment
for
itself
and,
after
the
execution
its
supposed
to
clean
up
the
environment.
We
we
do
this
to
make
the
granularity
of
tests
and
the
atomicity
of
tests
to
prevent
the
situation
when
one
test
will
affect
other
tests,
not
cleaning
up
the
dirty
environment
and
the
data
used
for
this
particular
test
execution.
This
could
affect
other
tests.
That's
why
all
the
M
FGF
tests
supposed
to
clean
the
data
after
itself?
A
A
A
A
A
A
A
A
A
C
C
C
C
A
A
So
the
test
which
you
want
just
show
you
not
all
the
tests
we
we've
written.
So,
for
example,
you
can
see
that
we
recovered
a
lot
of
photos
on
our
activism
fgf
test,
but
taking
into
account
that
image
after
test
needs
some
time
to
be
executive,
so
just
to
prevent
the
situation
when
you
would
be
bored
look
and
looking
at
all
our
tests
beyond
executed.
A
This
shows
just
several
of
those,
but
along
with
them,
we
have
quite
a
lot
of
open
to
requests
covering
different
test
scenarios,
and
now
slava
will
also
show
you
how
we,
how
he
created
as
a
test
scenarios
and
described
them
from
a
cheap
test
and
for
those
who
for
those
test
scenarios.
We
actually
write
this
MFD
F
test.
So
now
flower
feel
free
to
share
your
screen.
D
I
will
show
you
our
hip
tests,
we're
working
on
writing
scenario
to
cover
functionality
of
Messiah
and
I,
open
it
folder
for
this
functionality
of
recorder
with
negative
quantity,
and
here
you
may
see,
we
have
scenario
to
check
that
different
types
of
products,
simple
virtual
and
whatever
they
work
in
not
a
simple
end.
Yet
in
Neutron
and
they're,
working
on
with
this
function
of
negative
authors,
output
of
threshold,
twist
combination
with
recorder
and
I
will
not
maybe
take
a
lot
of
time
to
show
you
all
steps
of
the
test.
D
But
here
we
have
like
called
here
action
word
that
it's
that,
like
new
source
created,
stop
created
category
created,
then
product
itself
created,
and
then
we
do
our
action.
It's
called
when
the
example
that
you
set
negative
outer
stop
hold
you
recorder.
You
said
that
before
and
then
you
get
sellable
quantity
on
the
stock.
Like
hundred
fifty,
what
you
saw
on
commercial
test
and
the
same
procedure,
we
do,
we
do
four
different
up
product
is
rate
and
without
right,
and
also
here
we
check
that
only
its
left
called
is
working
as
well.
D
Another
folder,
it's
about
my
section
on
products.
It's
still
on
work
and
also,
after
yesterday,
grooming
some
new
features.
They
are
on
horizont
to
be
added
to
this,
because
yesterday
it
would
agree
that
for
transparent
area
to
source,
not
only
quantity
will
be
transferred,
but
also
auto
stock
status
and
some
other
things-
and
here
you
may
see
that
there
are
tests
with
several
product
with
different
types
of
products
to
assign
product
sources
to
an
assign
product
sources
to
transversal
venturi,
and
also
check
that
stock
status
is
also
transferred.
A
So
now
you
see
that,
along
with
creating
new
functionality
for
magenta,
we
are
also
carefully
documented
and
the
cover
with
different
kind
of
testing,
because,
along
with
longer
ISM
fgf
testing,
along
with
acceptance
testing,
we
also
covered.
For
example.
Here
here
was
a
request
which
emerged
yesterday,
where
Alessandra
Oren
she
provided
integrational
test
for
backorder
functionality
where,
where
he
on
the
level
of
integration
tests
covered
different
cases
when
the
warrior
and
the
negative
threshold
is
used
and
covered
to
it
with
with
PHP
unit
and
the
and
magenta
integration
testing
framework.
A
A
Here
it's
very
important
to
make
sure
that
the
filter
for
MSI
part
2
is
checked,
I
fixed
the
links
for
then
hub
bored
when
wherever
is
possible
wherever
I
found,
but
just
just
to
make
sure
that
you
have
this
filter
applicable
because
Helens
is
filter.
Actually
you'll
see
the
board
for
milestone
two
and
actually
a
current
board
represent
the
actual
state
of
deals
and
the
the
tickets
which
are
which
are
beyond
process
now,
and
the
tickets
which
are
available
for
for
contributors.
A
A
And
here
you
see,
all
the
tickets
are
estimated
and
all
of
these
tickets
represent
the
backlog
for
milestone,
part
two
and
also
last,
but
not
the
least.
Today
we,
we
published
one
more
article
and
this
article
this
article
about
the
module
structure
in
magenta
homicide
where,
where
I
described,
actually,
why
do
we
have
an
in
MSI
four
modules,
instead
of
one
so
module
for
API
contracts,
module
implementation
of
module
for
admin
UI
and
for
fronting
di?
A
So
here
you
can
see
this
article,
which
describes
a
modularity
for
which
is
the
idea
described
here,
are
applicable
for
all
Magento,
not
just
for
MSI,
but
you
can
see
the
proper
implementation
of
this
ideas
currently
just
in
MSI.
So
here,
for
example,
you
can
see
that
we
have
three
modules:
inventory,
inventory,
admin,
UI
and
inventory
API,
but
usually
in
magenta,
for
example,
you
can
you
just
see
one
module
four
catalog,
but
there
are
no
catalog
admin,
UI
catered
API.
A
So
all
the
all
the
logic
doing
in
two
different
application
layers
like
presentation,
layer
like
layer
of
service
contract
and
the
layer
of
business
project.
All
of
this
logic
now
located
in
one
module,
but
in
MSI
we
applied
the
single
responsibility
principle
for
on
the
module
level.
That's
why
we
end
up
having
the
structure
and
in
this
article
I
described
all
the
pros
we
were
given,
and
there.
A
Is
a
possibility
how
easily
MSI
could
be
extended
or
customized
by
third
party
developer?
So
here
you
can
see
it
and
I
I
decided
to
do
it
because,
especially
recently,
there
were
several
several
questions
about.
Why
do
we
have
this
module
structure?
What
the
cross,
what
the
benefits
we
get?
We
get
using
this
module
structure
and
also
this
new
module
structure
specially
heaven,
dedicated
API
modules,
would
be
described
soon,
as
an
architectural
recommended
way
for
all
magenta
to
design.
A
So
I
recommend
you
to
look
through
this
services
article
because
it
would
be
it
would
be
useful
not
just
from
not
just
for
those
who
follow
MSI,
but
for
those
who
write
proper
for
those
who
want
to
write
the
proper
modular
solution
based
on
magenta
to
so
that's
actually
all
from
my
site,
and
that's
probably
all
for
today
demo.
These
are
any
any
open
question.
We
would
be
ready
to
answer
them.