►
From YouTube: Magento MSI Open Demo. December 14, 2018
Description
Agenda:
- @Tom Erskine Test Coverage update. Test cases and MTFT acceptance tests.
- Elasticsearch support on Custom Stock
- Fix performance degradation on Search and Category pages
- Question regarding Source Deduction on Credit Memo
- @Richard Bayet from Smile will make a demo of integration Smile Elasticsearch with MSI
B
Okay,
Igor
can
confirm
seeing
PowerPoint
on
my
screen:
yep,
okay,
great
okay,
so
quality
testing
status
update
as
of
today
not
a
lot
of
changes
coming
through,
but
we'll
run
through
the
important
bits.
So
in
terms
of
our
manual
testing,
this
is
where
we've
had
some
change
from
last
time.
Our
last
week
report
had
505
tests
in
total,
we've
increased
that
to
531
defined
tests
in
head
tests.
All
the
new
tests,
of
course,
have
been
run
as
they've
been
created,
all
of
those
created
within
the
seals
component.
B
As
we
can
see
here,
that
number
has
jumped
to
204.
That
has
been
a
response
to
scenarios
we've
defined
after
there
were
some
bug
fixes
around
seals
and
particular
credit
memo
scenarios.
So
the
failures
and
the
fixes
that
we
saw
in
the
last
two
weeks
have
not
been
obviously
tested
as
they're
PR
fixes
come
in
and
they
are
actual
manual
testing
defined
for
those
so
that
they
will
be
covered
as
we
go
forward.
Automation
for
the
s0
s1
priorities
of
those
will
be
coming
off.
B
B
In
terms
of
our
automation,
then
how
we're
looking
on
that?
As
I
say,
the
priority
is
automating
the
s0
s1
scenarios.
So
currently
that's
142
automated
scenarios.
We
obviously
want
to
take
those
newly
created
manual
scenarios
for
the
credit
memos
and
push
them
across
and
do
the
automated
there's.
Also
efforts
ongoing
in
unskipable
tasks,
we'll
see
the
number
of
those
so
currently,
as
we
see
the
severity
breakdown
is
around,
there
see
Rose
s
once
in
component.
B
This
does
much
proportionally
around
what
we
have
with
the
test
coverage
defined
for
the
manual
regression
runs,
and
we
want
that
SEALs
figure
to
come
up
and
then,
in
terms
of
this
execution.
So
the
good
news
is,
it's
all
passes
and
skips
were
misses
being
run
dearly,
so
we're
not
seeing
any
failures
out
of
the
automation
and
so
that's
stable.
However,
am
that
skip
number
we
want
to
bring
down?
There
are
active,
PRS
I
to
unscathed
between
eight
and
twelve
tests,
so
hoping
for
our
next
report.
B
A
You
Tom
so
the
next
one
gonna
be
presentation
of
support,
elasticsearch
adapter
for
custom
stock,
because
you
know
that
since
magenta
to
the
treated
oh,
we
move
elasticsearch
to
the
Community
Edition
and,
along
with
that,
we
duplicated
the
previous
adopters
of
the
my
sequel
adapter,
which
is
no
longer
consider
it
as
a
default
one,
and
is
that
a
recommended
one?
And
as
you
know,
that
at
the
time
of
release
magenta
to
the
street
at
all,
the
support
of
elastic
storage
was
only
provided
for
default
stock.
A
So
today
we
will
demonstrate
the
work,
how
the
elasticsearch
supports
the
custom
stock
created
created
on
MSI,
and
we
will
demonstrate
the
main
functionalities
of
search
so
that
quick
search,
advanced
search,
layered
navigation
and
the
category
page
and
the
sava
will
demonstrate
all
of
that.
So
I
feel
free
to
share
your
screen
and
demonstrate
how
we
support
elastic,
search
with
MSI,
hello,
everyone.
A
C
First
of
all,
I
will
start
from
that.
Each
charge
have
been
tallied.
I
used
this
del
doc
interaction
and
probably
I
will
up
ought
to
do
this
shot.
I
will
send
this
link
into
the
chart.
It
is
so
I
work
on
Ubuntu,
for
this
and
I
said
I
downloaded,
erotic,
church
service
and
run
it
on
my
system
and
afterward.
Hurtin
me
when
I
haven't
at
by
intent
of
magenta
I,
should
do
set
in
configuration
page
on
italic
Kingdom.
C
Okay,
here
catalog
search
settings
and,
as
you
may
see,
I
said
elasticsearch.
We
have
choice.
My
city,
real
elasticsearch,
elasticsearch,
five,
ghost
I
have
just
elected
sorry,
because
I
hope
service
to
point
four
point:
six
version
and
I
have
the.
If
everything
said
properly,
I
have
successful
test.
It
is
so
let
us
go
to
our
case
work
of
gnostic
church
on
custom
stock.
For
this
I
have
created
two
sources:
custom
sources
and
new
stock
wish,
assign
it
to
main
website,
and
I
have
assigned
to
sources.
C
C
Now
let
me
go
to
my
category.
First
of
all,
we
have
problem
that
category
page
was
not
working
at
all
and
we
could
not
see
any
products
assign
it
to
custom
source.
It
is
you
may
say
that
category,
a
category
page
working
and
I
have
available
my
free
products
here,
simple
for
the
one
simple
product
to
and
configurable
prod
on,
the
left.
C
C
C
C
A
A
In
any
case,
this
pull
request,
definitely
because
it
in
fluent
too
many
functional
areas
and
because
this
George
France
knowledge
of
magenta
is
not
not
only
the
source
because
the
catalog
by
category
and
the
category
layer
it
navigation,
if
that's
also
all
about
search,
so
that
we
will
definitely
test
this.
Who
requests
very
carefully
before
to
bring
it
to
the
to
this.
D
A
A
So
since
imagine
two
to
the
three
that
all
release,
my
sequel,
adapter
is
deprecated
and
in
our
plans
we
will
remove
my
sequel,
adapter
out
of
search
adapters
since
magenta
2.4
at
least.
We
would
have
this
possibility
to
remove
and
currently
the
we
actually
that's
why
we
move
from
magenta
magenta
immunity,
juice,
adapter,
and
now
we
consider
that
elasticsearch
adapter
supposed
to
be
with
or
for
default,
magenta
deployments.
A
A
So,
let's
go
to
our
next
item
in
the
agenda
and
they
see
that
vitaliy
is
not
on
the
call,
so
probably
I
will
make
the
presentation
on
behalf
of
Italy.
So,
first
of
all,
let
me
thank
you
vitaly
from
advocate
aleppo,
who
made
a
footprint
in
this
performance
performance
track,
and
he
delivered
the
first
request
and
I
will
I
will
show
you
the
results
and
I
showed
it.
What
what
the
goodness
this
request
brings
to
agenda
with
MSI.
Let
me
share
my
screen.
First.
A
So,
just
from
the
from
the
beginning,
let
me
yeah,
let
me
tell
you
a
couple
of
words
regarding
the
route
case
and
where
we
have
the
reasons
for
this
performance
degradation.
So
you
know
that
since
MSI
we
have
the
mechanism
which
we
call
the
distributed
indexes
that
we
build
and
create
independent
indices
for
each
virtual
aggregation,
which
we
call
stocks
in
MSI,
and
currently
we
support
just
limited
product
types
to
to
be
included
in
this
aggregation.
A
So
currently
we
don't
support
bundled
products
on
custom
stocks
so
that
we
support
all
other
product
types
except
the
bundle
one
and
the
bundle
product
support
is
implemented
just
for
the
full
stock,
so-called
single
stock
mode
and
for
the
default
stock.
What
we
do
we
make
it
fall
back
to
the
existing
legacy
index
created
by
the
Catholic
inventory,
and
this
index
is
represented
by
the
table.
Catwalk
inventory
underscore
stock
underscore
status,
so
the
catalogue
inventory
stock
status
table
and
to
make
the
index
follow
the
same
interfaces.
I
mean
my
signal.
A
The
same
interfaces
as
our
custom
indexes
and
finally,
we
realized,
but
actually
not.
Finally,
we
realized,
but
we've
seen
based
on
our
performance.
Acceptance
builds
that
we
have
a
performance
degradation
because
of
the
my
sickle
usage,
because
the
Mexico
usage
introduces
two
additional
joints
to
all
the
standards
to
all
the
standards.
A
So
here
we
expect
that
the
degree
of
the
root
cause
of
the
degradation
is
based
on
the
usage
of
this
not
efficient
query,
which
involves
my
sequel
view,
which
leads
to
additional
joints
not
using
indexes,
but
here
on
a
product
page.
The
root
cause
is
a
bit
different.
The
root
cause
is
usually
of
additional
services
so
to
make
to
make
a
check
whether
the
product
is
saleable
or
not.
We
we
provide
in
MSI,
we
provide
additional
services,
and
these
services
introduce
validation
chain,
and
the
validation
chain
consists
of
several
additional
checks.
A
So
probably
the
main
reason
for
this
kind
of
degradation
we
see
here
is
that
is
that
quad,
so
this
degradation
is
based
on
additional
code,
but
not
bicycle
price.
So
also
we
had
the
problem,
so
you
can
see
that
the
problem
was
on
a
category
page.
You
can
see
that
category
page
degradation
that
Samson
areas
was
almost
200
percent
and
also
you
see
that
also
the
search
scenario
was
affected.
So
in
the
scope
of
the
pull
request
created
by
vitaliy,
let
me
demonstrate
uses
pull
request.
A
A
So
last
degradation
on
a
simple
product
is
disappeared
so
because
it's
less
than
3%,
we
considered
that
it
gets
to
the
standard
deviation,
because
we,
our
test
environment,
doesn't
provide
the
exact
exact
timing
because
it's
subject
of
environment,
it's
subject
of
current
load
of
processor
and
the
memory.
That's
why
we
consider
if
this
deviation
is
less
than
3%.
A
For
our
single
stop
mode,
the
degradation
not
such
a
gradation
is
not
applicable
for
custom
stocks
because
for
custom
stocks
we
don't
use
any
Mexico
use,
so
we
use
real
indexes
and
for
in
the
case,
when
we
use
real
indexes,
we
don't
experience
any
degradation,
because
we
all
the
joints.
We
do.
We
do
using
the
bicycle
indexes.
So
this
is
pretty
pretty
pretty
performance
efficient
way
of
doing
germs
and
doing
all
the
musical
operation.
That's.
Why
also?
A
We
consider
that
as
soon
as
the
bundle
product
support
would
be
added
and
we
no
need
any
reason
to
use
Mexico
view
anymore,
the
older
form
of
degradation
gun
after
that.
So
currently
we
consider
this
performance
fixes
as
a
as
a
way
to
provide
really
hot
fixes
to
the
market,
just
to
prove
just
to
avoid
any
blockers
for
merchants
to
upgrade
on
magenta
to
the
tree
that
always
NSI.
So
this
is
the
main
reason
for
this
at
hot
performance
fixes.
So
now,
let's
consider
other
values.
A
So
this
is
this
is
built
for
current,
so
you
can
see
modern,
MS
and
magenta
to
the
tree
that
all
release
plus
MSI
these
values.
So
these
values
are
for
for
fixing
magenta
soda
per
day.
We
still
experience
the
degradation,
but
this
degradation
is
much
less
than
it
was
before
and
the
lasts.
So
you
can
see
the
degradation
and
search
like
100%.
A
Here
we
have
12%,
so
we
were
still
working
on
other
root
causes
for
the
degradation
and
the
Steep
on
who
is
currently
on.
The
calls
of
the
guy
who
asked
me
questions
several
minutes
ago
is
a
contributor
who
also
work
on
this
track,
so
we
we
expect
that
we
have
even
better
values
pretty
soon,
but
this
is
a
current.
Our
current
results
and
I
believe,
even
with
these
results
we
can
make,
we
can
make
next
package
of
MSI
and
bring
it
to
the
market
just
to
provide
to
provide
an
ability
to
boost
magenta
with
msi.
A
So
this
is
actually
was
an
update
from
vitaly.
So
I
was
talking
on
behalf
of
italy,
so
he's
a
guy
who
made
that
happen,
and
now
now,
let's
follow
our
agenda
next,
the
next
topic
in
our
agenda
yeah.
So
we
had
a
question-
and
this
is
a
product
question-
to
mark
her
Guardians
regarding
the
stock
deduction
and
working
with
one
of
our
contributors
working
this
week.
A
We
found
next
issue
today
and
actually
the
issue
is
bit
tricky
interesting
one.
So,
let's
consider
the
situation
when
we
we
have
some
number
of
products
in
the
stock
and
customer
place
in
order,
for
example,
buying
five
five
items
of
of
some
specific
askew
and
after
that
the
the
whole
order
is
invoiced.
A
So
let's
say
we
enroll
made
invoice
for
five
items
and
after
that
merchant
for
some
reason
decided
to
make
the
refund
so
merchant
proceeding
with
the
credit
memo
and
making
the
credit
memo
merchant
does
not
does
not
apply
check
box
for
a
return
to
stock.
So
currently,
in
this
case,
our
system
literally
makes
nothing.
So
we
just
complete
an
order,
but
we
don't
contain,
say
the
reservation
and
what
we
do.
A
This
is
not
happen
with
this
order
so
that
the
our
our
cleaning
mechanism
will
not
will
not
clean
out
this
reservation
and
actually
all
other
reservation
created.
For
this
ask
you
and
the
country,
we
have
a
proposal
how
to
fix
it,
but
this
is.
This
is
actually
pretty
interesting
business
case
to
discuss,
because
in
this
particular
business
case,
so
merchants
merchants
probably
had
a
situation
that,
at
the
time
when
the
order
been
placed,
he
considered
that
he
has
enough
enough
products
to
fulfill
this
order.
A
A
Probably
this
is
just
just
the
case
when
probably
some
products
just
pulled
on
the
warehouse
and
that's
why
he
can't
he
can't
ship
them,
so
he
just
returning
money
to
the
customer
composite
and
what
actually
we
need
to
do
in
this
case,
because
probably
my
suggestion
in
this
case
that
we
we
have
to
compensate
the
stock
reservation
and,
along
with
that,
we
have
to
make
the
source
deduction.
So
we
need
to
remove
this
spoiled
product
from
warehouse,
but
currently
because
we
don't
have
any
source
selection
algorithm
here.
A
E
A
If,
if
order
being
shipped,
it
will
ready,
we
already
support
this
functionality
and
there
is
no
any
problems
with
it
because
at
the
time
of
shipment,
the
source
been
deducted
and
the
stock
being
compensated
with
compensation
or
reservation.
So
we
handled
this
business
case
very
good.
But
actually,
currently
is
the
issue
just
with
the
with
the
orders,
which
was
invoiced,
but
not,
but
not.
E
E
E
E
E
E
E
A
E
E
D
A
E
It's
interesting
because
it
doesn't
it's
not.
It
needs
to
tie
to
what's
happening
physically
with
the
inventory,
but,
like
you
said,
it's
it's
quite
an
edge
case,
because
you
would
only
leave
that
unchecked
if
something
had
happened
that
spoiled
or
damaged
the
inventory
before
it
had
even
been
shipped
and.
E
A
E
E
But
at
this
point
now
we
have
to
make
a
source
if
it's
unchecked,
so
the
checked
case
is
fine.
If
it's
unchecked,
we
have
to
make
a
source
deduction,
but
we
can't
line
up
with
what's
happening
physically.
So
if
there's
three
sources
in
the
stock,
they
all
have
some
quantity
in
stock
that
it's
physically
sitting
on
the
shelf
and
those
three
sources.
E
It's
just
gonna
pick
whatever
is
the
top
one
and
deduct
in
your
example:
five
they
may
not
actually
reflect
the
one
where
the
the
the
stock
has
been
damaged.
Of
course,
the
merchant
has
the
ability
to
it's.
It's
really
an
edge
case,
because
it's
unlikely
that
this
would
happen
and
they
can
correct
it
by
going
in
and
adjusting
quantities
between
sources
if
they
need
to.
F
E
E
G
E
Could
it
could
be
quite
confusing
if
I
don't
check
this
box?
What's
gonna
happen?
Is
there's
gonna,
be
a
stock
deduction?
Sorry
a
source
deduction
made
against
one
of
the
sources
in
the
stock.
Don't
the
most
priority.
But
it's
not
immediately
obvious
to
me
from
this
page.
That's
what's
gonna
happen,
so
I
can
go
in
and
correct
it,
but
I
don't
even
know
that
I
I'm
gonna
need
to
go.
Take
that
step
to
correct
it.
H
H
Because
I
have
a
use
case
for
this,
but
it
will
be
long
to
explain
that
like
I
would
have
to.
I
would
need
to
affect
the
reservation
to
some
stock,
because
after
I
have
to
do
the
ASIC
translation
with
an
external
system,
and
it
seems
to
have
a
similar
use
case
here.
So
I
was
wondering
if
that
was
possible
like
affected
an
atomistic
or
a
default
stock
before
the
device
selection
at
the
shipment.
E
H
In
my
use
case,
it's
like
I
have
on
some
external
system
which
contains
the
start.
The
source
stocks,
tax
and
I
am
synchronizing,
those
so
start
with
the
start
of
Mercia
amazon
tow.
But
when
there
is
an
order,
you
you
create
a
reservation
system
and
the
system
I'm
using
a
sorry,
also
have
a
reservation
system,
but
they
will
have.
They
will
need
the
need
to
have
the
stack
on
the
reservation
under
system
is
bind
to
the
stub,
giving.
H
A
Actually,
you
can
talk
to
Paul
Hoffman.
You
probably
seen
that
guy
his
active
participant
of
a
Maasai
community
so
he's
about
to
release
all
module
and
they
they
want
to
introduce
the
source
level.
Reservations.
Mmm-Hmm
looks
like
what
would
you
need
the
source
level
reservation,
so
that
would
be
along
with
the
stock
level
reservations.
A
He
wants
to
use
his
source
level
reservation,
especially
for
the
case
when
they
integration
with
your
PC
Stan
happens:
yeah
reserve
some
amount
of
product
for
particular
warehouses,
all
right
thanks
these
guys.
This
guy
is
in
MSI
section.
Also
you
can
ping
directly
or
via
them
and
I
said
channel
so
death
yeah.
E
A
E
We
need
to
make
a
compensation
or
reservation
against
the
stock
hmmm,
which
is
a
change,
and
then
we
need
to
do
a
source.
Deduction
I
think
make
it
using
the
priority.
Based
algorithm
makes
the
most
sense,
it's
the
most
obvious
thing,
and
then
maybe
we
look
at
having
a
modal
that
comes
up
so,
if
I
submit
this
form
and
I
did
not
check
return
to
stock
and
there
have
been
no
shipments.
A
A
So
could
you
please
create
the
ticket
because
we
agreed
that
we
would
not
create
before
the
meeting
so
just
to
finalize
with
you,
so
now
we're
pretty
clear
what
we
need
to
implement
so
so
please
create
corresponding
ticket
and
send
mark
just
to
review
of
the
old
acceptance
criteria
and
last
but
definitely
not
least,
presenter
for
today
will
not
be
Richard
from
smile
agency.
Who
will
demonstrate
you,
the
integration
and
the
extra
customization
of
smile
extension
for
elasticsearch
and
how
this
extension
supports.
Custom
stops
on
multi-source
inventory
so
Richard.
A
A
A
A
A
A
A
A
A
I
I
I
I
I
I
Ok,
and
so
now,
the
problem
is
that
my
Wells,
that
is
located
in
France
for
Europe,
is
empty,
so
there
should
be
no
change
for
the
US
side
and
my
back
is
category
for
the
French,
the
European
side.
Isn't
it
so
I
need
to
assign
some
inventories
so
I'm
going
to
cheat
a
bit
I'm
going
to
move
all
my
stock
form
the
default
source
to
the
European
one,
so
I'm
going
to
transfer
my
inventory
I'm
not
going
to
do
that
for
all
of
them.
I'm
going
to
check
on
me.
I
I
I
I
To
make
it
short
quicker
at
10
next
time
we
have
vertical
data
sources
and
one
of
the
data
sources
is
the
one
immunity
to
the
stock
which
we
pulled,
the
stock
status
and
the
stock
quantity
and
this
model
simply
pays
not,
which
is
the
resource
model.
That's
at
same
just
you'd,
the
dapi.
It
used
the
stock
reserve
interface
and
it
also
used
the
stock
index
table
table
name.
I
It
is
over
interface
because
when
we
index
we
index
for
all
products
or
a
selection
of
products
in
the
context
of
a
star
ID
so
from
that
is
quite
a
bit
straightforward.
With
from
the
store
or
a
store
ID,
we
guess
the
website
ID
and
for
the
website
ID.
We
use,
we
guess
the
stock
ID
food,
a
stock
with
over
interface,
and
when
we
have
the
stock
ID,
we
use
the
stock
index
table
provider,
to
guess
the
name
of
the
table.
I.
A
Got
it,
and
actually
this
definitely
makes
sense
from
the
performance
point
of
view,
but
what
we
need
to
be
clear
that
currently,
is
this
value.
In
you
know,
stock
tables
actually
does
not
come
does
not
contain
the
reservations
so
because
we
keep
all
the
reservation
separately
and
that's
why
we
use
for
the
precise
calculation
of
the
sale
ability
and
for
the
precise
calculation
of
the
get
product
saleable
quantity.
We
usually
use
these
two
services
I
sent
in
select
channel
so
how
this
services
work.
A
They
get
the
data
from
the
tables
you
mentioned
and
applies
all
the
reservation
on
top
and
after
that
they
actually
get
the
sale
ability
status,
but
we
in
magenta
we
usually
actually
we
do.
The
same.
I
mean
that
for
the
category
page
and
for
the
and
for
the
search
result
page
with
we
use
just
tables
not
apply
and
all
the
reservation
just
to
provide
the
results
as
soon
as
possible.
So
potentially
it
can
be
a
CPS
and
when
you
will
see
the
product
in
the
search
result
page.
A
I
A
So
this
is
actually
pretty
interesting,
whether
you
go
into
apply
reservation
like
whether
we
have
plans
to
apply
a
reservation
for
your
index
data
or
you
will
you
will
do
as
you
do
right
now.
So
just
just
say
that
is
a
key
not
to
apply
reservation,
so
have
some
data
little
bit
stale
and
just
apply
like
because
in
any
case,
at
the
time
when
the
product
gonna
be
added
to
the
shopping,
cart
or
if
the
given
user
will
navigate
to
the
product
page,
we
any
case
magenta
will
check
the
correct
state
of
the
product.
A
A
If
not
looks
like,
we
are
good
for
today.
Sorry,
we
little
bit
exceeded
the
initial
time
we
plan
to
spend
for
today's
meeting,
but
that
was
cool
that
there
are
different
topics
to
be
demonstrated
today.
So
thank
you
very
much
for
for
your
time,
especially
especially
thank
you
for
assured
that
our
guests
on
the
demo
meeting.
Thank
you
for
your
really
interesting
presentation
and
don't
wait
week
to
another
meeting.