►
Description
Integration testing is always a difficult area. You need to make sure that all system dependencies are prepared, data is correctly initialised for each run and test runs do not interfere with each other. Even with tools like the Arquillian Framework, writing integration tests can be a complicated task and the act of maintaining large sets of tests can become a nightmare if there’s not enough knowledge of all dependencies involved.
With the Testcontainers project, convoluted and complicated integration tests can be a thing of the past. A test container allows you to create reliable integration tests covering a wide range of scenarios like using databases, microservices interactions and even GUI and user experience testing. One of the important factors for the success of this framework is the usage of Docker containers to create a reliable reproducible environment for each test, which separates the dependencies and the application code in a way that it is easy to maintain for developers.
This talk will showcase the basics of Test containers, how to create quick integration tests for some common scenarios and will use both Payara Server and Payara Micro to test sample enterprise Java applications.
-
Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.
Learn more: https://jakarta.ee/
Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/
A
Hello,
everyone
welcome
to
easy
Java
integration
testing
with
test
containers
for
simplifying
integration,
test
for
Enterprise
Java
I'm,
father
tereso,
I
work
as
service
manager
for
viral
Services
Limited.
One
of
the
organizations
that
belong
to
the
Jakarta
group-
and
you
hopefully
know
about
what's
in
some
in
some
form,
I
am
based
on
the
beautiful
city
of
Barranquilla
here
in
Colombia
on
the
other
side
of
the
world
nice
to
be
here
again.
A
B
A
Just
to
reiterate
what
you
probably
know
about
Opera
Services
being
members
of
the
eclipse
Foundation,
we
work
in
a
conjunction
with
other
companies
and
organizations
in
order
to
push
Jakarta
to
you,
know,
The
Innovation,
making
sure
that
our
user
base
and
our
customer
base
understand
what
they
want
and
making
sure
that
Jakarta
is
catching
up
with
times,
but
also
part
of
the
Community
member.
So
we
are
committee
members
of
the
break
management.
A
A
A
If,
for
example,
your
application
depends
on
a
specific
database
and
that
database
has
vulnerabilities
reported
or
it
has
limitations,
or
it
has
known
issues
that
may
affect
your
production
environment
or
the
way
that
your
application
works
in
its
operational,
let's
say
context,
then
you
have
to
be
aware:
okay,
what
happens
when
those
updates
and
what
those
components
have
to
be
in
place
so
something
that
I
forgot
to
mention,
because
I
jumped
right
into
the
talk.
If
you
have
any
question,
please
save
them.
A
For
the
end
of
my
talk,
I'll
be
very
happy
to
answer
any
questions
that
you
guys
have
so
back
to
this
again.
The
main
integration
testing
Frameworks
in
Java
are
based
on
unit
testing
Frameworks
like
a
unit
test
and
g
spots,
but
most
of
the
integration
testing
Frameworks
are
highly
Dependable
on
the
platform.
So,
for
example,
spring
has
its
own
spring
testing
framework
that
is
based
on
well,
it's
compatible
with
the
three
that
I
mentioned.
A
There
are
all
the
Frameworks
designed
with
their
own
testing
Solutions,
and
some
of
them
are
compatible
with
all
the
solutions
and,
of
course,
there's
always
the
prevalent
of
running
mocking
tests.
In
the
case
that
you
may
or
may
not
be
aware,
the
let's
say
premise
of
mocking
a
test
is
to
simulate
interactions
between
components
without
the
need
for
you
to
have
a
proper
component
or
a
proper
dependence
in
place.
A
Server
or
to
run
a
complex
system
in
order
to
test
how
it
works,
you
simply
simulate
how
they
interact
between
each
other,
based
on
some
preconditions,
which
is
not
necessarily
bad,
but
for
real
word
testing
or
for
a
real-time
scenario.
It's
not
the
best,
because
you
are
simply
making
sure
that
the
simulated
condition
works
in
the
way
that
you
intend
to,
but
we're
usually
scales,
and
that
won't
help.
A
A
Now
that
Jakarta
is
fully
open
source
and
the
community
is
working
towards
like
one
goal
of
getting
it
to
where
it
needs
to
be,
then
maybe
in
the
future
will
start
seeing
some
proposals
of
specifications,
but
in
the
meantime
there
is
nothing
that
can
help
us
standardize
testing
or
provide
some
think
that
you
can
use
in
order
to
test
multiple
environments
provided
by
multiple
Jakarta
eventers
middle
size.
Footprint
has
been
reduced,
a
lot
which
is
good
before
application.
Server
runtimes
were
super
heavy
and
they
were
big.
A
Now
they
are
relatively
small
in
the
sense
that,
yes,
they
are
still
under
100
megabytes,
even
closer
to
550
megabytes
both
of
them,
but
that
is
not
necessarily
bad
because
the
cost
of
storage
and
on
cloud
native
storage-
it's
not
necessarily
that
expensive.
So
that's
something
that
can
help
as
well
Implement
environments
where
you
need
a
mill
work
to
be
available,
but
the
main
challenge
is
the
complex
environment.
A
It
was
developed
by
it
was
a
while
back
I
think
it's
still
part
of
the
overall
ecosystem
of
Java's
tools
and
it's
it's
focused
on
creating
a
Pandora
agnostic,
kind
of
way
of
testing
Jakarta
components
in
that
you
create
something
called
a
shrink,
wrap
test,
and
that
test
is
prepared
against
a
general
specific
adapter.
You
make
sure
that
all
of
that
is
set
up
before
a
test.
Suite
is
ready
to
run.
A
Then
you
run
the
test
with
making
sure
that
that
pre-packaged
application
plus
runtime
environment
gives
you
results
that
you
want
for
your
test,
which
is
not
necessarily
bad,
but
in
this
particular
case,
for
example,
you
want
to
test
a
Jakarta,
a
runtime.
You
need
a
container
specific
adapter
for
that
runtime
and,
if
it's
not
available,
then
you
have
to
read,
write
it
and
maintain
yourself.
A
If
that's
something
that
you
want
to
based
on
your
integration
testing,
environment-
and
this
adds
complex
within
writing
tests,
because
you
not
only
you
need
to
make
sure
that
your
tests
are
written
in
a
way
that
you
can
find
the
issues
in
your
applications,
especially
when
integration
testing
is
concerned.
But
you
also
have
to
be
concerned
inserting
correctly
the
packaging
of
these
applications
and
making
sure
that
our
the
conditions
are
met
for
the
Arcadian
test
to
run
correctly.
A
Here
is
an
example
that
I
have
using
yeah
unit.
Four.
Do
you
have
an
artillion
test
called
percentile
test?
You
are
testing
a
data
object
subject.
You
know
for
all
those
are
old
now
from
there
with
that
pattern.
That's
just
simply
an
Access
Data
object
that
allows
you
to
interact
with,
in
this
case
personal
data,
so
you
have
an
AGB
on
a
stable
screen
that
allows
you
to
create
and
interact
with
the
data
of
the
buttons
in
the
system,
and
you
are
injecting
in
this
guest
test
data
that
you
want
to
verify.
A
If
that
is
correctly
so
for
a
client,
the
easiest
way
to
set
up
a
test
is
just
to
create
a
shrink
wrap
package.
In
that
case,
you
are
giving
it
a
war.
File
in
this
case
would
be
the
application
Word
file
in
this
case-
name
rklene
Dash
example,
you
add-
or
in
this
case
I'm
creating
this
with
the
classes
in
the
corresponding
project.
A
I'm,
adding
these
two
classes,
the
person
classes
that
corresponds
to
The
Entity
of
the
database,
regulated
at
the
percentile
class
and
I'm,
adding
a
resource,
in
this
case
a
Tesla
system,
XML
that
corresponds
to
persistence,
deployment
descriptor
for
the
Jakarta
resistance,
API
that
contains
how
my
classes
are
mapped
to
the
corresponding
database
tables
and
all
the
persistence
configuration
of
the
application.
But
in
this
case
the
test
is
just
simply
concerned
to
okay.
Before
everything
that
you
need
to
prepare
that
the
data
is
ready,
in
this
case,
okay,
how
do
I
prepare
this?
A
That's,
not
the
concern
of
the
test,
that's
something
that
you
have
to
make
sure
for
the
test
to
correctly
run
and
the
test
itself
is
okay.
I
want
to
see
if
all
of
the
persons
that
I
am
retrieving
from
the
database
in
this
case
is
correct
or
in
and
in
this
case
Okay.
The
data
that
I
prepare
only
has
one
person
in
there.
A
So
you
retrieve
all
of
this
using
the
all
of
the
person
objects
using
the
kettle
method,
make
sure
that
it's
a
list
of
size
one
and
that
it
contains
a
person
whose
name
is
John
Malkovich,
for
example,
and
in
this
case
well
the
test
day.
Data
is
just
of
a
pendant
class
that
I'm
using
in
order
to
simulate
how
data
will
be
created,
and
in
this
case
you
can
see
that
I'm
not
actively
using
any
database.
The
only
thing
that
I'm
doing
is
tricking
the
arcelian
engine
to
make
sure
that,
oh,
whenever.
A
Retrieving
the
data
in
particular,
so
that
leaves
some
gaps
to
be
filled.
So
you
have
to
assemble
a
part
of
the
application
to
test
it.
You
can
just
simply
grab
your
application
in
the
natural
state
that
it
should
be
shipped
or
promoted
as
a
test
or
a
QA
or
production
bill.
You
know
you
have
to
grab
the
application
and
assemble
it
in
some
form
to
make
sure
that
a
part
of
it
is
functioning
in
the
way
that
it
should.
A
This
includes
all
of
the
codes
and
resources
that
you
need
for
that
application
to
work
correctly,
and
in
this
particular
case
you
are
tested
a
persistence
layer,
but
not
this
store.
You
are
not
concerned
itself
on
what
database
you're
using
what
happens
if,
tomorrow,
your
application
is
being
migrated
from
a
particular
database
engine
to
another
because
of
Market
reasons
or
because
you
want
to
change
your
licensing
model
or
because
you
or
organization
is
just
simply
forcing
you
to
make
that
change.
A
So
all
the
builders
need
to
be
written
with
that
in
mind,
but
in
this
particular
case
the
application.
This
doesn't
reflect
that,
so
there
is
no
way
to
test
either
again
that
and
you
can
test
different
configurations.
What
happens
if,
for
example,
you
need
to
fine
tune
parameters
to
making
sure
that
the
application
is
still
reacting,
the
same
way,
functional
and
speaking,
absolutely
not
so.
This
is
not
a
real
word
in
a
sense,
it
is
an
integration
test,
but
it's
not
something
that
is
akin
to
what
you
are
going
to
encounter
in
the
real
world.
A
C
A
This
also
allows
you
to
ease
the
networking
setup
because
creating
docking
containers
are
leaving.
The
same
network
is
really
easy
because
again,
the
docker
and
the
container
technology
itself
has
become
highly
intuitive
in
that
way,
in
that
it
created
a
container.
It's
just
really
simple:
setting
up
a
network
and
making
the
continuation
data
very
simple
as
well.
This
allows
you
to
also
test
data
access
layers.
Oh
so
I
need
a
postgresql
database.
Cool
I
create
a
positive
SQL
container,
set
it
up
in
a
way
connect
my
application
runtime
to
it,
and
that's
it.
A
Oh
do
I
need
to
switch
that
up
to
my
SQL
runtime,
no
problem,
you
just
simply
reconfigure
the
container
to
be
on
my
SQL
container
and
reconfigure
the
parameters
to
making
sure
that
that
connection
is
available
and
voila,
and
this
takes
advantage
of
the
portability
of
Docker
itself
to
make
sure
that
your
integration
tests
are
fully
portable.
I
am
putting
on
starting
there
because
there
are
some
caveats:
there
is
no
100
portability,
but
you
can
be
as
Portables
as
you
can
within
this
environment,
so
it
benefits
as
I
mentioned.
That's
our
user
Focus.
A
So,
instead
of
concerning
yourself
on
making
sure
that
oh
the
developer
can
create
a
test
that
they
can
use
Now
setting
the
container
is
easy.
Then
the
test
itself
is
oh,
how
is
the
user
expected
to
interact
with
this
application?
Will
they
create
this
object
or
will
they
log
into
the
application
and
get
a
result?
What
happens
when
D
logging
credentials
are
not
correctly
in,
and
in
that
idea
you
see
a
star
simulated
user
experience.
A
Testing
or
user
access
and
testing,
so
you
can
do
effective,
Black
Box
testing,
because
again
you
are
not
concerning
yourself
well,
creating
the
runtime.
The
runtime
is
already
provisioned
with
you
and
it
exists
on
a
Docker
container.
It's
not
necessarily
Black
Box,
because,
depending
on
how
accessible
that
container
is
you
can
even
access
it
in
mid
testing
in
order
to
make
sure
that
things
are
going
well,
you
can
run
a
even
at
security
audits
if
possible.
A
Oh,
what
happens,
for
example,
you
want
to
make
sure
that
your
product
and
your
application
follows
a
set
of
security
standards
and
it's
up
to
a
acceptable
threshold
of
oh.
There
are
no
vulnerabilities
reported
in
these
components
and
there
is
no
way
to
penetrade
or
run
a
remote
code
execution
attack
seconds
on
a
particular
application.
A
That's
something
that
you
can
do
and
you
can
automate,
because
in
this
way
you
can
quickly
switch
up
containers
based
on
the
specific
patch
releases
of
whatever
technology
you're
using,
and
this
allows
you
to
identify
flaws
in
these
specific
Technologies
in
the
sense
that
oh,
what
happens
if
I
am
running
a
particular
database
server
or
I,
there
are
specific
errors
in
that
database.
Server
I
need
to
upgrade
okay
cool.
A
Then
you
have
to
apply
a
particular
app
but
actually
upgrade,
and
then
your
integration
test
might
completely
be
green
or
or
baby
pass,
so
test
containers
are
really
simple
to
set
up.
The
only
requirements
are
that
you
need
to,
of
course,
have
Docker
available
and
at
the
moment
of
test,
containers
only
supports
Linux
containers
with
the
support.
Windows
containers
are
not
yet
supported,
sadly,
but
for
the
purposes
of
testing
itself.
A
This
is
not
a
big
deal,
because
most
tested
environments
can
be
created
quickly
in
Linux
servers
and
any
Cloud
environment
or
or
cloud
service
that
you
can
find.
The
test
Frameworks
at
the
moment
are
supported,
like
you
need
four,
and
five
and
Spock
testing
is
not
supported
at
the
moment,
and
you
need
to
be
some
have
some
the
knowledge
of
Maven
and
Gradle,
because
the
way
that
you
set
up
the
projects
itself
and
the
dependencies
is
through
this
Bill
project
or
these
project
management
tools.
A
C
A
Get
started
in
unit
5,
you
only
need
to
add
the
dependencies
for
for
the
unit,
in
this
case
I'm
using
the
API
and
the
engine
on
version.
5.8.1
I
know
that
is
not
the
latest,
but
for
the
purposes
of
the
demo,
that
will
be
showing
that's
what
I'm
using
test
containers
itself
at
the
moment,
it's
up
to
version
17.6.
So
in
this
case
this
is
no
far
off.
A
You
need
to
add
the
corresponding
test,
containers,
API
and
the
corresponding
gauni
Jupiter
integration
with
the
technology,
which
is
this
case
with
BJ
unit
5..
So
how
do
you
set
up
a
test
container?
It's
really
simple
on
a
test
Suite
that
you
write
that
test
suit
needs
to
be
annotated
with
ad
test
containers.
This
is
not
the
of
man.
This
is
not
a
mandatory
solution,
but
this
will
allow
the
test
containers
engines
to
manage
the
life
cycle
of
your
containers
in
a
way
that
is
simple.
A
Once
you've
run
the
test,
the
test
containers
engine
will
start
or
containers
and
they
will
kill
containers
once
the
desert
run.
Basically,
some
considerations.
This
way,
you
don't
need
to
manually
start
and
stop
your
containers.
If
you
have
that
particular
need,
depending
on
your
requirements
of
the
whether
you
want
to
structure
an
integration
test,
that's
something
that
you
can
do,
but
this
is
not
mandatory,
so
you
create
a
container
pass
it
a
Dockery
machine
which
is
an
object
that
uses
the
traditional
Docker
image.
A
A
That
I
have
an
application
name.
F3
is
on
my
app
as
a
Docker
image.
I
am
running
it
with
this
batch
shell
script
and
automatically
the
container
will
start
running
and
a
simple
test
is
just
making
sure
that
the
container
is
running.
So
you
just
show
is
through
or
run
make
your
assert
sorry
that
the
mic
app
container,
which
is
the
object
of
the
general
container
instance
in
here,
is
running.
Pretty
simple.
A
A
more
complex
case
is
that,
okay,
you
want
to
make
sure
that,
once
your
container
is
running,
you
can't
get
a
response
from
HTTP
endpoint
or
a
red
service
in
this
case,
so
you
fire
up.
Okay,
I
want
to
get
the
URL,
then
fire
response
and
get
a
status
and
making
sure
that
I'm
getting
to
oh
okay,
and
then
you
can
just
simply
do
oh
assets
equals
that
whatever
response
I'm
getting
is
that?
A
A
Otherwise
you'll
have
to
wait
and
you
determine
number
of
or
on
a
specific
amount
of
time,
until
the
content
is
ready
to
run
the
tests
and
sales
because
otherwise
is
still
getting
provision
and
that's
important
because,
depending
on
how
fast
is
load,
the
runtime
that
you
are
dealing
with
this,
this
will
vary.
So
you
can
also
wait
for
a
specific,
lock
message
on
the
output
of
the
container
and
that
will
simplify
the
way
that
the
container
is
running.
A
What
about
dependencies?
So
dependencies
are
important
because
in
this
particular
case,
let's
say
that
you
want
to
connect
your
runtime
to
your
database.
Let's
talk
about
the
mySQL
database
and
in
this
example,
I
am
creating
another
container
called
TV
container,
and
this
is
container
based
on
my
sql8
I.
Am
configuring
it
using
some
default
settings
or
with
password
a
username,
a
password
for
that
username
and
a
database
name
and
importantly,
I-
want
this
container
to
be
speaking
to
my
runtime
or
be
accessible
by
my
server
runtime.
C
A
A
So
let's
say
that
back
to
my
app
container
I
am
then
configuring
that
same
container
on
the
same
network
say:
oh,
it
will
depend
on
that
TV
container,
meaning
that
this
container
won't
start
and
won't
be
provision
until
the
first
one
is
ready
already
has
been
started
and
then
I
can
configure
my
application
with
whatever,
and
they
prefer
way
is
usually
environmental
viral,
so
system
properties,
but
I
am
establishing.
Oh,
the
database
server
will
be
located
at
the
Alias
of
that
container
and
I'm
provisioning.
All
of
the
other
attributes
and
settings
that
I
showcase.
A
This
way
I
can
quickly
connect
to
containers
on
the
same
network
and
allow
my
runtime
to
use
a
database
with
no
difficulties.
As
I
mentioned.
Desk
containers
has
official
database
support
for
rotational
databases.
They
have
particular
modules
as
they
call
them
or
with
that
comes
with
prepare
special
objects
for
wrapped
containers.
For
my
SQL,
my
LED
Oracle
Express
Edition
32
postgres
nosql
Solutions,
like
couchbase
mongodb,
neo4j
Cassandra.
A
There
are
many
others
and
if
you
do
not
have
a
solution
in
here,
anyone
can
create
a
module
that
can
make
the
light
easier
when
they
prepare
the
test
and
to
use
this
modules
you
can
just
simply
add
the
dependencies
on
your
code.
So
for
that
particular
Maven
project,
these
are
the
dependencies
for
the
MySQL
module.
So
you.
A
Container
itself,
I
think
in
the
case
that
you're
interacting
with
the
container
itself,
PHA
ABC,
for
example,
then
you
need
the
MySQL
DBC
driver
and
the
way
that
you
create
a
container
in
this
way
is
just
specifying.
Oh
I
want
a
MySQL
container,
not
a
genetic
container,
and
then
you
reconfigure
and
notes
that
I'm
not
passing
any
properties
in
here
for
the
passwords
of
the
username.
A
The
container
will
provision
everything
for
me
and
I
can
obtain
these
values
by
just
simply
calling
the
MySQL
container
get
user
get
password
and
get
database
name
methods
that
way.
I
am
not
concerned
with
provides
and
Sample
credentials.
Because
again,
all
of
this
is
on
on
our
test
environment.
So
that
is
not
something
that
I
should
worry
about.
A
A
That
is
also
support
for
other
Solutions
modules
for
elasticsearch
Apache,
Kafka,
Rabbi,
main
Q,
solar
and
genes,
toxic
proxy
Etc,
many
multiple
Solutions
in
the
market
arrogance,
as
I
mentioned,
you
can
create
your
own
custom
module
if
there
is
something
that
you
need
for
your
particular
environment.
So
some
caveats
Docker
adds
an
extra
layer
of
processing.
A
Again,
Docker
needs
additional
resources,
memory
and
CPU
power
in
order
to
run
this
container,
so
resources
will
be
needed
for
full
cooperation
depending
on
how
big
your
integration
tests
gets,
then
that
will
increase
the
overall
time
of
the
test
itself
so
of
all
the
integration
tests
and
stuff.
So
you
have
to
be
careful
import,
your
team,
all
of
these
resources
for
a
test
environment
middleware,
must
be
prepared
for
Docker.
A
So
if
you're
using
a
solution
that
doesn't
have
a
corresponding
Docker
container
support
image
support
and
you
will
have
to
create
your
own
and
the
dependencies
for
those,
but
mostly
everything-
every
popular
or
commercial
gold,
commercial
and
Community
Solutions
have
documented
support
in
some
way.
So
that's
not
necessarily
a
big
deal
and,
lastly,
Black
Box
testing
is
not
suitable
for
all
software.
Sometimes
you
want
to
test
the
components
and
see
what's
happening
inside
and
Docker
containers
are
not
maybe
the
best
way
to
do
this,
but
that
will
depend
for
most
Enterprise
Java
applications.
C
A
Another
way
to
test
this,
there
is
a
solution
called
test
containers
Cloud
that
is
offered
by
the
people
that
develop
the
test
containers
project.
You
can
try
to
get
access
to
this,
because
it's
a
really
good
service,
where
you
don't
need
a
local
Docker
environment
to
run
your
test.
You
can
just
simply
run
the
test
and
Outsource
them
to
separate
Cloud
instance.
That
is
already
prepared
for
you.
A
That
will
run
your
tests
and
if
you
want
more
informations,
you
can
just
go
to
this
containers
cloud
and
see
for
yourself
and
try
to
get
access
to
the
service
as
well.
So
I
will
show
a
quick
demo.
It's
located
on
GitHub
or
my
personal
account
under
conference
demo,
and
the
demo
is
a
really
simple,
Jakarta
application
that
this
is
a
demo
that
I
showcase
on
most
of
my
detox.
A
That
I
did
it's
composed
of
three
services
of
three
microservices
that
are
used
in
order
to
create
conference
sessions
and
manage
the
sessions
that
will
be
held
in
a
conference
either
online
or
presses
whatever,
because
it's
inspired
by
the
really
old,
let's
say
micro
profile
application
that
was
created
with
that
mine.
So
This
research,
these
three
microservices,
are
a
session
service
that
will
allow
you
to
create
the
session
talks
and
speaker
service.
A
A
As
you
can
see,
this
uses
an
application
pad
nothing
complicated.
It
has
an
API
endpoint
of
a
speaker
resource
that
will
allow
you
to
create
the
speakers
and
I
will
I
will
allow
you
to
see
the
data
of
the
speakers
check
that
speaker
success.
It
also
contains
some
neat
micro
profile,
open,
API
definitions.
A
C
C
A
Time
to
make
verify
that
all
the
tests
are
green
at
the
moment,
so
that
would
be
a
really
good
point
for
for
you
to
talk,
so
the
woman
is
using
Jakarta,
9
and
micro
profile
4.1,
so
in
particular,
this
session
test
the
service.
Sorry,
the
session
service
behaves
mostly
the
same
way,
so
I
will
be
jumping
to
the
build
service,
and
this
one
is
a
bit
more
complex
in
that
it
uses
definition
for
that
data
source.
That
depends
on
a
mySQL
database.
A
So
in
this
case
all
this
application
doesn't
use
the
embedded
data
source.
It
uses
an
external
data
source
for
a
database
that
runs
MySQL
and
it
requires
a
database
user,
a
password
and
AJ
ABC
URL
to
be
configured
in
this
way.
So
I
can
externalize
the
configuration
of
my
data
source
once
I
deploy
this
service
on
fire
micro
and
in
particular
these
Services.
Also,
this
one
delete
both
application.
Service
will
require
the
session
service
because
in
order
to
build
full
sessions,
you
need
to
create
those
sessions
and
query
the
data
of
those
sessions.
A
So
these
three
services
integrate
with
each
other
the
session
service
depends
on
the
speaker.
One
and
the
both
service
depends
on
the
session
one,
so
there
is
a
dependency
of
source,
so
let's
quickly
show
an
integration
test.
Let
me
show
the
speaker
test
in
this
case,
so
how
do
I
create
a
quick
integration
testing
here,
so
I
I'm,
creating
this
speaker
Service
Test
class,
as
you.
A
A
In
this
case,
this
is
a
static
field
in
another
interface
that
it's
just
a
documentation
name
created
from
the
standard
via
a
micro
image
for
Via
5.2022,
which
is
argument
Edition
0.4
that
has
KFC
k17
support.
So
technically,
this
is
a
by
a
micro,
5.23.2
2022.4
that
runs
for
JK
17.,
so
back
to
including
here
in
particular,
you
can
see
that
once
I
create
a
generic
container,
I
can
configure
that
whatever
one
so
I
want
to
expose
HTTP
480,
which
by
default
is
the
HTTP
ordered
by
a
micro
exposes.
A
Then
I
have
to
copy
the
deployment
of
my
application
to
that
container,
because
that's
how
prior
micro
and
Docker
works
so
I
deploy
this
application
by
just
simply
grabbing
a
mountable
file.
This
is
just
a
way
of
mounting
a
local
file
to
the
file
system
of
the
container,
so
I
just
create
a
mountable
file
instance
and
pass
it
a
host
pad
in
this
case.
Oh
all,
of
the
files
all
of
the
wire
files
for
the
services
are
in
the
Target
Wars
file.
C
A
Once
this
application
model,
endpoint
is
ready
and
you
can
get
an
all
status
quo
from
that
one.
Then
you
know
that
your
application
is
deployed
and
it's
ready
to
receive
requests.
So
you
deploy
the
application
by
specifying.
Oh
I
want
to
run
this
Docker
container
with
this
command,
deploy
all
pile
deployments,
microservice,
speaker
wire
and
that's
it
I,
just
simply
give
it
a
context
root
and
that
application
should
be
deployed
immediately.
C
A
Four
yeah
there
we
go,
and
in
here
you
can
see
that
test
containers
is
from
The
Suite
one
stack
test,
containers
star:
you
can
see
that
it's
using
Docker
desktop
because
it's
running
locally,
it's
specifying
the
API
and
the
server
mention
that
I'm
using
and
you
can
see
that
it
will
start
the
container
for
by
our
micro,
Five
Point.
Twenty
twenty
two
point:
four:
seven
to
get
AK
17
it's
waiting,
60
seconds
for
the
URL
that
I
mentioned
to
be
ready
and
again
it
automatically
Maps
the
port.
A
Because
that's
something
that
you
can
do
once
the
container
is
ready.
Then
the
test
will
start
running
and
you
can
see
oh
they're,
all
passing,
because
that's
how
it's
configured,
interestingly
I,
have
confused
my
test
to
run
in
a
particular
order,
because
I'm
reusing
this
container
test
containers
allows
me
to
run
whatever
container
I
create
and,
as
an
instance
variable
will
get
started
and
stop
for
each
test
method
of
my
test
suit.
But
that's
a
bit
too
much
and
a
bit
Overkill,
because
I
want
to
create
a
speaker,
verify
that
I
added.
A
It
then
get
the
data
and
then
verify
that
data
that
I
haven't
put
in
there-
it's
not
in
there.
So
if
I
Define
the
container
as
a
static
field
of
that
or
a
static
variable
of
that
particular
test
suit,
then
the
container
will
be
created
once
and
then
it
will
be
started
once
before.
All
the
test
has
run
and
it
will
be
stopped
once
all
of
the
tests
are
completed,
so
I'm
reusing
the
same
container
for
that
test,
Suite
pretty
simple
to
do
so,
because
I
don't
have
much
time.
A
Let
me
quickly
show
you,
then
how
it
would
look
for
a
more
complex
case,
so
in
here,
I
have
a
really
more
complex
case
for
the
both
service
test
and
in
here
I
have
the
three
services,
the
speaker
service,
the
session
service
and
they
both
service.
Remember
what
I
told
you
that
one
depends
on
the
other,
and
that
depends
on
the
first
one.
So
I
am
configuring.
A
All
the
services
are
containers
and
I'm
also
preparing
a
database
for
a
MySQL
container
and,
as
you
can
see
here,
I'm
using
database
for
my
sql8
I'm,
putting
that
on
a
network
and
giving
it
an
aliens
and
I
am
configuring
that,
as
a
way
of
oh,
it
will
run
in
this
network.
All
of
the
containers
are
running
on
network.
The
speaker
service
gets
a
particular
Alias
the
same
for
the
session
service.
A
The
way
that
this
service
is
an
interacted
with
each
other
is
that
I
am
configuring
environment
variables
for
micro
profile
properties.
In
this
case,
it
would
be
my
Corporal
rest
client
and
for
the
session
service
it
needs
to
know
when
some
Services
of
the
or
rest
endpoints
of
this
speaker
service
are
available.
Oh,
that
is
simple.
Just
simply
pass
that
environment
variable
and
set
it
up
to
you
this
URL,
because
this
is
the
Alias
of
that
container
and.
A
I
am
Computing
the
database
using
environment
variables,
I
am
creating
a
year
ABC
URL
using
the
Alias
as
the
hostname
I'm,
getting
the
database
name
from
The
Container
itself,
I'm
using
the
username
and
password
for
the
database
containers
themselves
and
have
not
provided
any
default
values
because
I
don't
care
about
those.
This
is
a
test
environment
and
everything
else
is
set
up,
mostly
in
the
same
way.
So
you
can
just
simply
start
this
one.
Let
me
run
it.
A
C
C
A
Starting
in
here
so
I
can
also
access
these
containers
while
they
are
getting
created.
You
can
see
that
this
is
at
the
container
for
buyer
micro,
and
this
one
is
probably
deploying
one
of
these
Services.
The
first
one
will
be
the
speaker
service,
and
this
will
simplify
the
way
that
it's
running,
so
let
me
get
back
to
the
containers
and
cells.
So
I
have
to
wait
a
few
minutes
until
everything
is
ready
and
ready
to
go
because
I
have
a
bit
of
a
power
of
machine.
A
A
C
A
It's
I
think
that
yeah
this
one,
it's
deploying
the
micro
service
boat.
So
technically,
this
containers
is
ready,
and
that
means
that
all
data
should
be
running.
As
you
can
see,
I
have
three
green
tests.
Four
five
six
all
of
this
are
run
and
if
I
go
back,
five
containers
they
are
attached.
Mostly,
the
rear
container
is
the
last
one
and
it
should
be
getting
a
stopping
up
in
a
few
details.
Yeah
because
everything
has
been
disconnected.
A
Oh
there,
you
go
that's
screenwolf
and
yeah,
but
everything
has
been
cleaned
up
in
a
matter
of
few
seconds.
I
have
created
a
really
complex
test
container
environment
and
that
allows
me
to
test
in
reality
what
I
want
to
do
and
a
fun
thing
is
that
I
can
quickly
show
you.
Let
me
run
the
terminal,
so
can
I
do
that
alt,
eight
or.
C
A
Yeah
I
feel
like
I,
won't
have
enough
time
to.
Let
me
quickly
do
this
exit
presentation
mode,
so
I
can't
create
or
simplify
my
code
by
doing
this.
This
is
something
that
I
have
on
a
separate
branch
in
this
code.
So
let
me
quickly
go
back
to
presentation
mode
and
instead
of
creating
that
containers
in
that
way,
I
can
create
my
own
container,
which
I
have
done.
I
have
created
my
by
a
micro
container
class
that
simplifies
the
way
that
I
am
preparing
the
container.
C
A
I
can
just
simply
specify
a
method
like
oh
I
want
to
create
my
container
with
a
specific
deployment
and
give
pointed
to
a
file
name
and
I
want
to
put
a
container
on
a
specific
internal
network
analysis
and
that
way,
I
don't
even
need
to
specify
how
one
might
continue
to
start,
because
inside
the
micro
contact
by
a
micro
container
class
I
had
set
all
of
this
up
and
the
way
to
create
my
own
module
in
a
way.
It's
simple,
my
prior
microcontainer
extends
generate
container,
which
is
a
class
from
test.
A
A
A
B
A
It
would
be
much
difficult
because
technically,
every
runtime,
every
Legacy
runtime
can
be
dockerized
in
one
way.
The
resources
to
do
that
would
be
extremely
difficult
because,
again,
all
the
Technologies
are
more
heavyweight.
They
have
a
bigger
footprint,
the
requirements
and
and
and
probably
the
what
is
unfold
different
architectures.
Now
that
everything
is
more
homogeneous
in
a
way,
so
the
it's
not
to
say
that
it's
impossible,
it
can
be
done.
You
have
to
make
sure
that
the
relationship
to
weight
well.
C
A
Might
be
easier
just
to
Simply
set
up
a
different
virtualized
environment
where
your
legacy,
application
or
technology
can
leave
and
that
way
that
you
can
get
easier
benefits
rather
than
just
making
sure
that
is
the
case.
If
performance
is
not
a
main
concern,
that's
something
that
you
can
consider
to
win.