►
From YouTube: Import/Export weekly call 7th March 2018
Description
Recording of the import/export weekly call from the 7th of March 2018.
This project focuses on the https://github.com/magento-engcom/import-export-improvements repository with the aim to provide some key bug fixes in the 2.3 release of Magento 2.
If you would like to get involved in the project please see the github issues or contact the Magento Community Engineering team for more information.
A
Alright,
come
I'll
start
okay,
cool.
This
is
the
import-export
we
could
call.
It
is
the
7th
of
March,
which
is
surprisingly
far
along
in
the
year,
always
shocks
me.
We
yeah
we've
got
a
few
updates
for
this
week,
which
is
good
and
then
I'll
do
a
bit
of
a
talk
about
integration
test.
Cuz
a
few
people
had
questions
last
time.
The
first
major
update
is
that
the
fix
for
the
images
has
been
merged,
which
was
one
of
the
largest
stories,
so
that's
now
merged
and
into
the
three
development.
A
Also,
since
Adam
can't
talk
I'm
off
to
his
update,
at
least
for
now.
The
the
task
41
with
to
do
with
the
bundle
can
change
quantity.
This
has
passed
the
QA
and
Matassa
or
green,
which
is
fabulous
and
is
in
QA
at
the
moon.
Anyone
has
picked
it
up
from
our
side
as
yet,
but
it
is
in
the
queue
which
is
great
to
hear.
So.
Thank
you,
Adam
for
your
work.
A
There
then
issue
number
40
Adam
raised
a
point
that
the
actually
you
probably
shouldn't
actually
be
on
the
store
view
level
and
so
I
have
contacted
one
of
our
core
architects.
I
think
I
included
Adam
in
that
email,
I
hope
they
did.
If
I
didn't
add
him
feel
free
just
to
message
me
about
that
and
I'll.
B
A
A
Issue
is
number
40,
which
is
to
do
with
products
online,
which
is
mapping
our
wares.
Here
we
go
it's
a
mapping
of
the
status
attribute,
and
so
it's
whether
the
status
attribute
should
store
hue
level
or
whether
it
should
be
on
the
website
scope.
At
the
moment,
it
is
only
website
scope,
which
means
you
can't
change
it
on
a
soar
view
level,
so
we're
checking
with
the
core
architectural
team
at
the
moment
to
see
if,
if
that's
desired
or
whether
they'd
like
us
to
change
it.
B
A
Adam
says
something
else
in
the
chair
which
I've
just
seen:
I
did
okay,
I
saw
I,
did
included
great
then
to
people
that
aren't
in
the
call
today.
At
the
moment
we
had
mosques
in,
and
we
have,
this
task
came
back
from
came
back
from
QA.
We
have
fixed
the
product
part,
but
their
customer
entropy
part
was
not
working
as
desired,
so
he
was
having
a
look
into
this
and
it
was
a
ie
specific
or
the
the
QA
person
used
the
enterprise
to
to
create
the
customer
attribute,
which
is
okay.
A
So
we
were
getting
what
Marcin
should
have
access
since
he's
Magento
employee,
but
we
were
getting
him
set
up
on
enterprise
just
to
test
it
in
the
same
way
and
I
had
any
issue
with
attributes
created
by
the
admin
section
that
they
didn't
set
up
the
backend
model
correctly
or
when
I
was
testing
I've
messed
up
the
backend
model.
So
my
gut
feeling
is
it's
something
like
that,
but
we
will
yeah
or
push
AB
for
that.
A
A
A
A
A
C
Referring
to
so,
if
you
import,
if
you
export
the
file
with
the
same
local
as
English
and
then
import
now,
it's
working
for
visibility,
the
country
and
in
general
for
our
things.
The
issue
was
the
string
to
lower,
but,
to
be
honest,
I
don't
know
exactly
what
fix
it
didn't
find.
The
code
I
just
know
that
I
tested
again,
and
it
was
working
so
currently
I'm,
working
only
on
the
fact
that
if
you
export
in
a
different
localized,
so
your
user
Army
in
hesitation,
it
doesn't
work
still
which
is
expected
so.
B
Night
to
test
the
the
import
with
a
different,
only
different
I
comments,
because
when
I
export
a
product
product
I
try
to
import
is,
there
is
no
problem
for
for
the
simple
data,
even
only
with
the
downloadable
product
product
and
ranan
I
have
to
test
the
import
on
a
different
area.
Commerce
to
understand
the
the
problem
of
the
the
double
no
comma,
sorry,
double
a
pixel.
B
A
B
A
He's
working
on
number
80:
the
issue
occurs
during
the
refresh
with
index
after
the
import
when
creating
a
bundle
product
in
the
admin.
It's
not
an
issue
only
during
import,
so
it
should
be
easy
to
back-trace
what's
happening.
What
the
difference
is
between
the
import
and
the
admin
section,
I
assume,
as
yeah
cool
fabulous
alright.
A
So
a
few
people
requested
some
testing
or
some
introduction
into
a
testing.
So
while
this
is
still
running
and
failing,
which
is
annoying,
you
know,
I
guess
is
because
I
had
bad
data.
I
will
just
run
through
some
of
the
basics.
So
what
we
have
is
we
have
a
multi.
We
have
under
dev
tests
integration.
This
is
where
we
keep
our
integration
tests.
A
The
way
I
set
it
up
is
I,
take
a
copy
of
the
PHP
unit,
dot,
XML,
dot,
test
file,
which
is
here,
and
basically
the
only
difference
between
the
two
I
specify
here
either
the
directory
r1,
in
this
case
the
catalog
import-export
directly
or
if
I
want
to
test
a
specific
file.
I'll
comment
out
the
directory
line
and
I'll
add
in
tell
it
to
import.
A
The
other
thing
to
do
to
get
them
up
and
running
is
under
ATC.
Take
a
copy
of
the
install
config,
my
SQL,
the
PHP
dot
dist
removes
the
doc
test
and
set
it
up.
So
in
this
case,
I
have
my
local
settings
and
one
thing
I
noticed
is
you
have
to
specify
an
empty
database,
but
the
database
has
to
be
there
just
needs
to
be
empty
or
should
be
empty.
A
To
start
with,
and
my
my
case,
I
just
took
the
default
and
created
that
one,
then,
after
that,
if
you
are
in
the
integration
folder,
you
should
be
able
to
just
run
the
PHP
unit,
add
bin
file
and
it
will
go
through.
So
you
can
see
you
can
see
here.
I
just
ran
it,
and
this
ran
all
of
the
import/export
files.
This
one
ran
an
individual
file
and
this
one
is
currently
running
the
catalog
one
and
failing
and
the
reason
it's
failing
is
because
it's
not
a
clean
install,
which
was
my
mistake.
A
A
Yeah
like
this,
if
I
want
to
run
the
import/export,
so
phpunit
tell
it
where
to
get
the
unit.
Testing
config
and
also
I,
also
limit
this,
because
I
don't
often
run
them
all.
So,
in
this
case,
I
can
tell
it
to
run
all
of
the
import
cattle
occupy
export
unit
tests
and
they
run
super
quick.
The
unit
test
integration
does
take
a
little
longer
yeah
for
most
of
us,
the
main
file
we
will
be
dealing
with
when
we
are
using
the
catalog
one
is.
A
This
product
test
file,
which
is
a
little
bit
confusing,
basically
it
uses
the
abstract
one
and
the
product
file
product
test
file
only
has
the
data
provider
as
well
as
some
special
asserts
for
specific
attributes.
In
this
case
our
image
attribute
testing
and
but
in
the
abstract
one.
We
have
this
test
export
file
which
uses
data
it.
A
A
It
will
then
modify
the
data
that
it
needs
to
for
the
specific
skills
you've
defined.
So
in
this
case
we
have
these
three
SKUs
here
and
then,
if
you
specified
it
through
the
array,
you
can
also
tell
it
to
skin
attributes.
The
example
we
have
of
this
of
skipping
attributes
is
in
the
product
image.
We
tell
it
to
skip
the
image
small
image,
thumbnail
media
gallery
attributes,
because
we
test
them
here
in
this
special
specific
attributes
assertion
they.
A
Basically
all
the
other
will
do
for
checking
the
attributes.
Is
it
will
just
do
it?
Does
this
at
value
equal
this
value,
whereas
in
the
case
of
the
images,
because
we
are
rewriting
the
image
pass,
you
cannot
do
an
exact
match,
so
we
can
only
do
a
containing
match
yeah.
So
the
the
execute
test
itself
will
just
use
the
product
resource
to
get
the
information
get
the
original
information.
Then
it
will
export
the
products
to
its
version
of
the
file.
A
C
C
A
A
A
A
This
is
also
where
it
does
like
the
cleanup
and
the
installation
here.
So
if
you
already
had
it
installed
and
didn't
want
to
reinstall
you
can
you
can
do
this
sort
of
stuff
here
as
well
here
it
initializes
the
application,
just
like
the
index
yet
like
that
the
index
of
the
my
brains
are
not
there
today,
the
index
of
the
the
actual
application
like
if
you're
running
them
front
end
of
the
Magento,
so
not
just
the
tests
either
stuff
but
I'm
interested.
A
A
C
A
C
B
A
B
A
C
A
B
A
What
was
it
the
export
that
had
it,
the
export
one
of
them
definitely
have
okay,
there
was
one
that
had
a
different
locale
attest
where
it
it
checks
to
see
that
they're
being
exported
or
imported
based
on
the
different
locality,
but
yeah
I
would
I
would
go
to
your
import
test.
Make
a
new
test
case
where
it
takes
sense.
The
locality
runs
an
export
changes,
the
locality
and
then
runs
the
import
from
that
file
and
then
validate
that
the
results,
as
expected.
C
A
A
test
case
itself
or
in
a
new
one,
I'm,
not
really
not
really
too
sure,
because
this
file
is
already
pretty
massive,
but
here
you've
got
the
example
of
like
a
non-default
store
and
stuff
like
that.
So
I
would
just
you
could
add
a
new
test
for
different
locality
stores
or
whatever
you
want
to
call
it
in
this
case.
Okay,
all
right,
yep,
okay,.
A
All
right,
then
I
guess
that's
pretty
much
it
I
would
be
yeah.
I
will
chase
up
my
sin
and
Peter
about
there
to
pour
requests
and
see
what
the
progress
is
there
and,
in
the
meantime,
I
look
forward
to
Frederico
and
Andrews
progressed
when
they,
when
they
arrive,
as
well
as
miracles
as
well
right,
yeah
and
as
always,
if
you
need
anything
reach
out
I'm
available,
often
especially
during
the
day,
EU
time.
As
well,
I'm
relatively
flexible,
so
I
can
make
some
time
for
for
you
guys
for
calls
or
anything.