►
From YouTube: Integration Testing for Offline Environments, session 2
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
B
So
a
test
pipeline
has
been
set
up
initially
to
prove
the
site
and
online
environment
testing.
It's
a
clone
of
the
actual
nightly
pipeline
only
to
get
lob
CI.
Your
mole
has
been
stripped
back,
so
we
could
focus
really
on
on
the
air
cup
job,
but
it
will
be
added
to
the
nightly.
So
what
I'm
going
to
do
is
I'm
going
to
kick
off
an
air
cup
job
and
an
Erica
CI
job
because
it
currently
takes
about
19
minutes.
So,
let's
just
kick
this
off
get
out.
B
Roman
has
been
picked
up
so
while
it's
rollin
I'll
take
you
through
some
of
the
changes
that
were
made
so
look
at
a
little
bit
technical
here.
So
first
off
she
interest
me
at
etiquette,
lab
3,
a
gem,
a
new
test,
since
the
scenario
has
been
set
up
air
cuts.
So
let's
have
a
look
at
what
that
looks
like.
B
B
B
We
do
need
to
get
lab
instance
on
this,
because
we
need
to
be
able
to
reach
poor
duty
with
the
headless
browser.
That's
driven
by
executing
the
selenium
tests.
However,
it
will
be
locked
down
sort
of
alert,
emporia
t
its
air-gapped,
but
like
demo
environment
seconds
network
here
is
one
that's
going
to
be
shared
between
the
gate,
Laban's
and
sun.
On
the
runner.
It's
an
internal
erica
docker
network,
and
it's
the
only
network
that
their
honorable
use,
but
I
can
go
into
in
more
detail
later.
B
B
B
Exits
one:
if
it
successfully
connects
on
exit
zero
if
it
fails
to
connect
which
Brousseau
ora
grandmas
at
the
spin
surrounded.
You
know
it's
slightly
more
verbose
here.
It's
been
surrounded
by
some
echo
comments
and
dropping
the
actual
output
of
of
the
field.
W
get
because
I
was
concerned
that
when
it
goes
into
the
pipeline,
should
pipelines
need
to
be
debugged
in
future,
the
W
get
failure,
maybe
packed
up
upon
as
a
sort
of
false
negative.
C
B
B
Okay,
so
first
changed
the
point
at
which
we
would
usually
installed
the
github
key
because
we're
currently
working
off
branches
and
our
changes
and
get
lob
and
then
ticket
Lobby,
and
there
are
a
few
temporary
build
steps
to
bring
down
the
branches,
build
and
install
the
catalog
qhm
built
the
github
queue
docker
image
very
much
temporary
once
the
changes
are
reviewed
and
merged.
Until
you
know
there
are
actual
repositories,
get
love
and
get
love
to
you.
D
A
A
D
D
B
Yeah
I
guess
the
balance
there
was
I,
couldn't
failures
versus
having
something
nice
load.
You
know
once
not
having
some
sort
of
false
positive,
such
as
somebody
comes
along
later
and
says:
hey
something's
failed
here
when
you
know
what
it's
designed
to
feel
as
that's
what
the
actual
air-gap
test
is.
So
ya
need
need
to.
Maybe
have
a
think
about
that.
B
Okay,
so
checking
in
on
the
pipeline.
It's
it's
executing
away,
so
we
have
started
kicking
off
the
test.
Its
created
earcup
Network,
which
is
internal,
kicked
off
the
test
network.
So
that's
gonna
continue
executing
and
what
would
like
to
do
is
show
you
wonder,
kicked
off
an
Oracle
sort
of.
We
know
what
to
expect
em.
B
The
runner,
which
is
running
on
the
entirely
corrupt
network,
so
we
can
actually
see
the
network
here
internal
true,
so
that
network
is
never
going
to
see
the
outside
world,
so
the
runner
runs.
A
similar
check
does
so
W
get
my
check
and
on
confirm
that
we
WF
from
from
the
runner,
then,
if
I
skip
to
the
bottom,
just
to
show
you
the
smoke
test.
Zero
failures,
everything
past
the
pipeline
itself
is
green.
The
job
is
green,
so.
B
B
D
A
B
E
Cool
questions
for
sure
I,
don't
wanna
interrupt
your
flow,
but
I
can
wait
till
a
good
breaking
point,
but
it
seemed
like
it
was
a
good
breaking
point:
okay,
sooo,
so
I
think
I
get.
You
know
it's
fitting
up
a
docker
container.
It's
shutting
off
access
to
the
outside
world,
except
for
inbound.
Eighty
I
get
all
that
it's
doing
the
the
air
gap
kind
of
test.
What
are
the
other
tests
that
it's
doing?
I
saw
something
on
the
the
baked
one
that
said
twelve
tests
or
something
like
that?
What
are
they
would
it
be?
E
B
E
It's
basically
just
a
traditional
smoke
test
you
would
use
on
for
any
where
you're
just
seeing
if
you
can
get
it
to
work
in
the
air,
gapped
environment
and
had
it
be
automated,
is
that
essentially
that's
it
Kevin
yeah?
It's
really
make
sure,
because
I
wasn't
following
it
first
and
anybody
watching
the
video
might
have
the
same
confusion.
So
I
just
wanted
to
ask
that
question.
I.
Think
in.
D
This
suite
of
tests,
these
smoke
tests
run
every
night
based
on
a
nightly
image,
there's
a
whole
set
of
additional
to
the
smoke
tests
that
run.
So
we
test
omnibus
doctor
everything.
So
this
will
just
be
part
of
our
normal
nightly
run
so
that
we
can
verify
there
are
no
regressions
for
offline
environments,
not
specific
to
secure
analyzers
necessarily,
but
for
the
whole
gay
lab
app.
B
So
d,
the
live
job
is
it's
runnin,
free
at
usual
setup,
get
lab
running
free
some
chef
chef
play
books,
etc,
set
myself
up
wireless
happenin.
Do
you
want
me
to
take
you
free
somewhere
if
the
changes
that
permeate
to
the
cold,
or
are
we
interested
in
getting
to
the
low-level
cold
or
we're
happy
enough
to
watch
it?
If
I
play
in
executing.
C
E
Defy
me
yeah,
unfortunately,
Ruby
is
I
mean
a
ruby
is
pretty
easy
to
read,
even
if
you
don't
write
it
so
like
I
was
able
to
follow
most
of
what
you
should
our
leader,
so
even
I'm,
not
a
ruby
developer
but
and
most
of
the
customers
working
with
us,
ruby
was
lower
on
their
list
of
priorities
for
languages.
So
you
that's
assuming
that
they're
not
you
know.
First.
B
E
Realize
this
is
an
NBC,
but
another
potential
improvement
might
be
to
I
know.
In
the
previous
demos
we
were
doing
the
double
you
get
in
that
air
gap
check
test
job,
but
since
this
is
something
that's
gonna
run
more
often,
another
potential
improvement
to
the
MVC
might
be
to
probe
a
couple
of
extra
force
force.
A
couple
of
other
port
checks.
E
E
D
And
to
make
sure
that
work
there
in
the
normal
nightly
pipeline,
there
are
what
four
dozen
or
so
jobs
that
are
executed
for
various
subsets
of
tests.
So
that's
why
here
we
don't
have
a
separate
air
gap
check
job,
because
all
those
other
ones
would
not
be
air
gapped.
It's
just
this
particular
job.
Has
the
air
gapped
code.
E
B
Yes,
so
I'm
going
forward.
Definitely
there
is
a
need
there
to
flesh
out
the
specs,
noting
the
current
test.
Suite
is,
you
know
what
it
could
be
do
but
being
expanded
automation
around
a
journalize
Ursa
test
projects,
but
I
guess
for
the
target
of
the
MVC
the
purposes
of
the
demo.
Our
focus
initially
was
just
just
on
the
smoke
chests.
Oh.
E
B
All
good
see,
I've
won.
One
of
the
tests
has
generated
a
runner.
The
runner
connected
to
the
air
gap
network
run
through
the
W
air
gap
check
dublicate
field,
so
yep
the
runner
itself
was
running
and
yeah.
So
it
looks
like
that
job
finished,
twelve
examples
for
serial
failures,
job
succeeded
and
the
pipeline
itself.
B
B
You
know,
and
initially
we
do
want
to
get
the
merge
requests
enticed
into
a
master,
forget
lab
and
get
lucky
a
when
it's
been
signed
off
and
reviewed
the
CI
job
we
want
to
get
into
the
nightly
pipeline
and
you'd
have
definitely
expanded
our
specs
in
terms
of
analyzers
and
on
test
project
coverage
and
the.
D
E
D
E
A
E
D
A
D
Either
way,
I
think
maybe
we
have
a
confusion
here
on
the
NBC
for
doing
a
demo
versus
MVC
versus
for
being
done
with
work
and
feeling
like
it's
in
a
good
state.
I
think
there's
still
work
to
do
getting
more
than
just
a
smoke
test
in
here.
I,
don't
I,
don't
want
to
be
too
generous
with
ourselves
we're
still
gonna,
even
if
we
don't
demo
again,
there's
still
a
lot
of
work
that
we're
gonna
be
doing
behind
the
scenes
to
make
sure
that
this
is
in
a
good
state.
Okay,.
A
E
E
Yeah
I
think
that's
great
I
think
we're
making
really
good
progress.
I'm
really
excited
to
see
these
tests
being
incorporated
into
the
automated
so
that
they
can
be.
You
know
great
foundation
for
building
upon
you
know
as
we
move
forward.
So
we're
aware
of
you
know
things
that
that
break
in
the
air,
graft
environment
or
regress
in
the
aircraft
environment,
so
I
am
sure
our
customers
will
be
very
excited
as
this
progresses.
So
I
think.