►
From YouTube: Magento MSI Open Demo. September 21, 2018
Description
Regression status update Milestone 2
A
Actually,
on
friday,
we
are
going
to
to
publish
our
first
package
of
magenta
to
the
three
that
all
better
and,
along
with
that,
we
are
going
to
publish
first
packages
of
magenta
milestone,
2,
so
there's
going
to
be
better
to
for
MSI,
and
now
we
are
working
on
a
package,
preparation
and,
and
actually
I
will
do
more.
Kale
can
share
a
little
bit
more
about
this
process,
but
firstly,
let's
start
from:
let's
start
from
from
some
graphics
and
I
will
show
what.
A
What
actually
gonna
be
released
in
the
scope
of
magenta
MSI,
milestone,
2,
so
on
on
the
msi
roadmap
page,
you
can
see
actually
all
the
features
which
we
release
in
the
milestone
1,
as
well
as
milestone
2
and
as
a
as
a
product
backlog
for
milestone.
2.
We
took
several
several
stories.
Some
of
them
were
finished
and
others
were
postponed
till
till
now
stone
3.
So
we
are
going
to
release
and
these
features
which
currently
merge
him
to
into
a
messiah
mainline
support
of
negatives
results
for
the
quarter.
A
Functionality
must
inventory
action
for
migration,
especially
useful
for
migration
of
the
full
between
the
single
stock
mode
and
multi
stock
mode,
and
actually
mass
inventory
action
happens
using
using
bulky
api
which
we,
which
were
implemented
on
other
community
engineering
project
heading
hidden
by
alex,
live
zoom
and
on
a
previous
demo
during
actually
demonstrated
how
how
can
be
a
lot
of
source
item
can
be
easily
migrated,
totally
asynchronously
using
a
rabbit
and
queue
under
the
hood
and
how
this
happened.
Firstly,
not
blocking
the
UI
working
like
a
charm
and
another
feature.
A
The
support
of
the
group
product
for
multi-sourcing
wanted.
These
three
features
are
implemented
and
go
to
the
scope
of
the
regression
of
msi
with
magenta
and
to
the
three
that
Oh
two
stories
which
we
were
working
on
for
quite
a
long
time
actually
adapt
ation
of
inventory
configuration
both
source
and
stock.
A
It
was
decided
to
postpone
the
implementation
of
this
story
because,
as
you
can
see,
we
have
a
pretty
big
chunk
of
work
done,
which
actually
includes
a
lot
of
lot
of
changes
like
seven
thousands
of
code
lines
to
be
changed,
but
actually
the
the
main
fear,
not
the
amount
of
code
which
was
which
was
affected,
but
actually
the
number
of
scenarios,
and
we
probably
would
be
unable
to
stabilize
work
of
magenta
with
with
these
changes.
So
it
was
decided
to
perform
this
feature
to
next
factories
until
next,
better
release
of
magenta
Amazon.
A
A
Probably
mark
can
tell
a
little
bit
more
about
repair.
Each
is
asian.
He
has
done
for
the
scenarios
which
were
created
by
Slava,
so
we
have
about
500
test
scenarios,
and
recently
we
made
the
reprioritization
to
increase
our
automation
test
coverage
mark.
Would
you
like
to
say
several
words
about
the
repair
installation
and
how
many,
how
many
people
on
scenarios
now
we
have.
B
B
So
here's
the
gist
ranked
by
severity,
so
we
have
187
that
are
s0
165
s,
192
s
3
and
8
bit.
Sorry
s
2
and
1/3
are
s
3,
so
this
pie
chart
here
covers
all
of
the
ones,
including
tests
that
have
already
been
automated.
So
we
don't
have
4
and
52
remaining,
but
you
can
see
the
distribution
across
the
priorities
here.
A
A
C
A
We
have
pretty
close
to
do
a
half
of
scenarios
be
uncovered.
Yes,
yep,
that's
much
better
than
1/3.
Actually,
that's
true,
okay,
so
also
along
with
that,
we
prepare
it
prepared
environment
on
cloud
because
all
the
regression
and
should
be
started
on
cloud
and
today,
actually
we
deploys
its
environment
and
cloud
and
try
to
run
this
environment
and
the
currently
we
start
with
the
locker
which
prevent
us
to
make
regression
Bob.
Now
we
are
trying
to
fix
this
broken.
Actually,
the
the
root
cause
of
the
broker
issue
from
for
us
is
infrastructural
changes.
A
A
D
Okay
under
humid
yep,
yes,
so
previous
four
previous
regression
cycle,
we
quit
all
the
packages
in
half
manual
approach
for
refer
this
regression.
We
prepared,
together
with
Magento,
develop
steams.
We
prepared
special
Jenkins
bills
that
automate
all
the
stages
of
creation,
compositor
packages
and
deployment
deployments
of
them
to
the
public
composer
repository,
and
we
are
finalized.
The
last
checks
on
our
staging
environment
and
going
to
publish
this
this
composer
packages.
As
so
musts,
we
will
confirm,
verifies
that
every
single
works
fine.
D
A
A
A
A
A
D
C
So
yes,
this
week,
we've
been
working
on,
basically
reverting
all
the
skipped
changes
that
we
did
last
week
to
stabilize
our
builds.
So
we've
been
focusing
on
unscripted
at
a
time
and
trying
to
keep
the
actual,
build,
stable
and
resolving
any
other
issues
that
have
popped
up.
This
is
the
story.
We've
been
kind
of
bucketing
everything
under
so
at
one
place
to
actually
look
for
all
of
our
work
in
the
latest
PR
that
Alex
was
referencing
here
1642.
C
We
currently
still
have
seven
skip
tests
or
msi
specifically,
and
then
we
have
this
list
of
six
tests
here
that
are
compatibility
issues
when
we
run
with
msi
multimode
enabled
with
other
tests
from
corporate
title
to
me,
so
we're
focusing
on
getting
all
of
the
msi
ones
unscoped.
These
are
the
ones
that
we
have
remaining.
This
list
is
a
100%
accurate
right
now,
because
we
have
a
few
PRS
in
progress
that
we're
going
to
try
to
get
merge
today.
So
when
they
all
come
together,
we
should
have
a
good'n,
build
the
five
tests
or
b2b.
C
Normally
we
have
seven
here
and
we'll
play
mode
again.
We
have
multiple
PRS
that
are
going
to
be
addressing
this.
This
PR
specifically
for
b2b
I'm.
As
you
see,
we
only
have
these
two
tests
remaining,
so
we
are
making
progress
and
headway
on
getting
art,
that's
actually
unstitched
and
dwindling.
This
lifts
down
now
the
ones
where
we
have
to
actually
do
merge
files
for
other
repos.
Those
will
take
a
bit
of
time
to
get
it
all
synced
up
to
those
project,
but
once
we
have
all
sides
synced
up,
we
have
B
to
B.
E
E
The
the
week,
the
the
previous
Friday,
we
had
27
tests
skipped
here
on
an
aside
multimode.
So,
as
you
can
see,
we're
really
dropping
this
number.
We
will
work
harder
to
get
rid
of
this
number
at
all.
Also,
what
I
did
I
did
before
every
snoot
MSI
test,
you'd
I
create
a
database
backup
then,
when
she
was
finished
and
all
on
the
site
has
finished
I'm,
applying
this
backup
with
the
clean
Magento
to
Magento
and
basically
after
suit,
we
have
the
same
magenta
without
any
configuration
entities
after
Ms
ice
you'd
finished.
E
It
allows
us
to
reuse
this
magenta
entities
to
different
tests,
which
sometimes
failed,
because
we
had
multi
mode
enabled
and
we
try
to
fix
that
in
tests
and
concrete
tasks,
but
we
failed
because
the
order
of
tests
always
changes.
So
if
somebody
will
add
one
more
task
to
list
magenta
to
msi
anywhere,
the
order
of
these
tests
will
be
changed,
so
we
cannot
predict
it.
So
I
decided
to
do
it
this
way
when
we
have
a
suit,
which
isolates
all
the
stars
from
other
types
of
trusts.
E
Will
I'm
working
also
make
some
changes
for
MTF
tests?
I
don't
have
much
yet
to
share
it
because
most
they
are
just
working
on
MFP
F
tests.
Probably
next,
like
speak
a
little
more
about
engine
tests
also
about
sample
data
tests.
I
talked
yesterday,
one
might
hang
with
dev
ops
team.
I
explained
them
why
we
need
to
increase
selenium
timeout,
so
they
now
understand
what
is
going
on.
Why
we
need
to
increase
this
number
and
tasks
they
have
from
today
is
in
progress
and
I
believe
they
will
deliver
this
as
soon
as
possible.
A
Thank
you,
and
actually
last
but
not
least,
gonna
be
our
community
here
who
helped
us,
especially
in
this
week
who,
who
was
with
us
24/7
for
last
5
days,
fixing
enormous
amount
of
bugs
which
were
prevented
us
from
starting
their
aggression.
Ladies
and
gentlemen,
Zurich
I
was
sure
we're
talking
about
someone
else.
Action.
F
Thanks
so
well,
actually
just
a
bunch
of
bugs
just
two
bucks,
so
thank
you
for
your
words,
but
actually
I
did
very
few
things.
Well,
I'm
going
to
share
my
screen.
Let
me
just
stop
three
too
many
desktops
here,
okay,
you
should
see
my
screen
well,
so
we
found
well
during
this.
These
last
days
we
finished
working
on
the
passing
math
sections,
as
it
was
said
before,
and
we
fixed
a
couple
of
issues
there,
because
we
discovered
the
scary
debt.
F
F
F
That
okay,
so
basically,
we
found
that
there
was
a
foreign
key
between
the
source
item
and
lost
document.
If
occasion-
and
this
Frankie
was
basically
housing
a
lot
of
issues
to
us,
because
when
we
transfer,
for
example,
the
inventory
we
unassigned
the
product
from
previous
source,
then
we
assign
to
another
source
and
when
we
do
this,
if
we
have
a
foreign
key,
basically
we
have
a
problem
because
the
old
Association
is
gone.
So
we
do
not
know
anymore
about
the
dual
configuration
so
with
eager.
F
We
decided
to
drop
this
foreign
key
and
to
keep
a
consistency
based
on
this
Korea
plug-in
on
the
suicide
and
delete
that
is
taking
care
of
keeping
the
lost
identification
table
clean.
So,
basically,
we
moved
from
one
database
consistency
to
an
application
consistency
that
I
think
also
helps
us
to
avoid
this
kind
of
harder,
pendency
based
on
DB.
This
was
the
first
one,
then
we
discovered
actually
just
for
a
chance
for
a
because
Igor
basically
discovered
that
there
was
a
problem
while
running
the
social
external
grid,
because
he
found
that
basically,
the
source
was
selection.
F
Algorithm
was
losing
the
fractional
part
when
you
order.
Basically,
one
product
with
a
with
a
decimal
quantity,
but
we
discovered
that
it
was
much
bigger
issue
because
we
discovered
that
you,
you
could
add
for
expire
working
installation
here.
I
want
to
show
you
basically,
if
you,
if
you
have
an
MSI,
a
clean
MSI
and
you
have
a
product
that
is,
is
not
configured
to
load
actual
quantities.
You
can
always
add
additional
quantity.
That
is
quite
annoying
because
I
can
create
several
inconsistencies.
F
So
we
get
two
solutions
here,
because
we
discovered
that
basically,
the
problem
was
that
MSI
was
plug-in
izing,
the
one
of
the
classes
that
were
converting
the
decimal
part
of
an
integer
part.
So
we
had
two
two
options:
to
fix:
that
class
by,
for
example,
saying
that
you
must
cast
do
int
when
you,
when
you
select
additional
quantity,
but
at
the
end
we
decided
to
go
for
another
way,
so
adding
one
new
check
in
the
validation
chain.
That
probably,
is
the
more
appropriate
way
for
the
MSI.
F
So,
basically,
now,
if
you,
if
you
have
this
patch
and
you
want
to
to
add
additional
part,
basically
you
get
an
error
and
and
I
think
it's
basically
everything
I
did
in
this.
In
this
last
days,
I
still
have
other
small
bugs
I
fixed
today,
for
example
this
one
because
we
discovered
that
we
get
this
kind
of
UI
problem,
but
is
just
a
small
fix,
but
we
also
have
this
kind
of
fix
and
I
think
it's
almost
what
I
did.