|
Note
|
This repository contains the guide documentation source. To view the guide in published form, view it on the Open Liberty website. |
Learn how to develop tests for your microservices with the Arquillian managed container and run the tests on Open Liberty.
You will learn how to develop tests for your microservices by using the Arquillian Liberty Managed container and JUnit with Maven on Open Liberty. Arquillian is a testing framework to develop automated functional, integration and acceptance tests for your Java applications. Arquillian sets up the test environment and handles the application server lifecycle for you so you can focus on writing tests.
You will develop Arquillian tests that use JUnit as the runner and build your tests with Maven using the Liberty Maven plug-in. This technique simplifies the process of managing Arquillian dependencies and the setup of your Arquillian managed container.
You will work with an inventory microservice, which stores information about various systems. The inventory service communicates with the system service on a particular host to retrieve its system properties and store them. You will develop functional and integration tests for the microservices. You will also learn about the Maven and Liberty configurations so that you can run your tests on Open Liberty with the Arquillian Liberty Managed container.
Run the following commands to navigate to the finish directory and run the tests:
cd finish mvn clean package mvn liberty:create liberty:install-feature mvn liberty:configure-arquillian mvn failsafe:integration-test
Look for the following output:
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running it.io.openliberty.guides.system.SystemArquillianIT
...
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.133 s - in it.io.openliberty.guides.system.SystemArquillianIT
[INFO] Running it.io.openliberty.guides.inventory.InventoryArquillianIT
...
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.297 s - in it.io.openliberty.guides.
...
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
...Navigate to the start directory to begin.
You’ll develop tests that use Arquillian and JUnit to verify the inventory microservice as an endpoint and the functions of the InventoryResource class. The code for the microservices is in the src/main/java/io/openliberty/guides directory.
Create theInventoryArquillianITtest class.src/test/java/it/io/openliberty/guides/inventory/InventoryArquillianIT.java
InventoryArquillianIT.java
link:finish/src/test/java/it/io/openliberty/guides/inventory/InventoryArquillianIT.java[role=include]Notice that the JUnit Arquillian runner runs the tests instead of the standard JUnit runner. The @RunWith annotation preceding the class tells JUnit to run the tests by using Arquillian.
The method annotated by @Deployment defines the content of the web archive, which is going to be deployed onto the Open Liberty. The tests are either run on or against the Liberty instance. The testable = true attribute enables the deployment to run the tests "in container", that is the tests are run on the Liberty instance.
pom.xml
link:finish/pom.xml[role=include]The WARNAME variable is used to name the web archive and is defined in the pom.xml file. This name is necessary if you don’t want a randomly generated web archive name.
The ShrinkWrap API is used to create the web archive. All of the packages in the inventory service must be added to the web archive; otherwise, the code compiles successfully but fails at runtime when the injection of the InventoryResource class takes place. You can learn about the ShrinkWrap archive configuration in this Arquillian guide.
The @ArquillianResource annotation is used to retrieve the http://localhost:9080/arquillian-managed/ base URL for this web service. The annotation provides the host name, port number and web archive information for this service, so you don’t need to hardcode these values in the test case. The arquillian-managed path in the URL comes from the WAR name you specified when you created the web archive in the @Deployment annotated method. It’s needed when the inventory service communicates with the system service to get the system properties.
The testInventoryEndpoints method is an integration test to test the inventory service endpoints. The @RunAsClient annotation added in this test case indicates that this test case is to be run on the client side. By running the tests on the client side, the tests are run against the managed container. The endpoint test case first calls the http://localhost:9080/{WARNAME}/inventory/systems/{hostname} endpoint with the localhost host name to add its system properties to the inventory. The test verifies that the system property for the local and service JVM match. Then, the test method calls the http://localhost:9080/{WARNAME}/inventory/systems endpoint. The test checks that the inventory has one host and that the host is localhost. The test also verifies that the system property stored in the inventory for the local and service JVM match.
Contexts and Dependency Injection (CDI) is used to inject an instance of the InventoryResource class into this test class. You can learn more about CDI in the Injecting dependencies into microservices guide.
The injected InventoryResource instance is then tested by the testInventoryResourceFunctions method. This test case calls the listContents() method to get all systems that are stored in this inventory and verifies that localhost is the only system being found. Notice the functional test case doesn’t store any system in the inventory, the localhost system is from the endpoint test case that ran before this test case. The @InSequence Arquillian annotation guarantees the test sequence. The sequence is important for the two tests, as the results in the first test impact the second one.
The test cases are ready to run. You will configure the Maven build and the Liberty configuration to run them.
Configure your build to use the Arquillian Liberty Managed container and set up your Open Liberty to run your test cases by configuring the server.xml file.
First, configure your test build with Maven. All of the Maven configuration takes place in the pom.xml file, which is provided for you.
pom.xml
link:finish/pom.xml[role=include]Let’s look into each of the required elements for this configuration.
You need the arquillian-bom Bill of Materials. It’s a Maven artifact that defines the versions of Arquillian dependencies to make dependency management easier.
The arquillian-liberty-managed-junit dependency bundle, which includes all the core dependencies, is required to run the Arquillian tests on a managed Liberty container that uses JUnit. You can learn more about the Arquillian Liberty dependency bundles.
The maven-failsafe-plugin artifact runs your Arquillian integration tests by using JUnit.
Lastly, specify the liberty-maven-plugin configuration that defines your Open Liberty runtime configuration. When the application runs in an Arquillian Liberty managed container, the name of the .war file is used as the context root of the application. You can pass context root information to the application and customize the container by using the arquillianProperties configuration. To allow connections to Liberty running in dev mode, set allowConnectingToRunningServer to true.
To learn more about the arquillianProperties configuration, see the Arquillian Liberty Managed documentation.
Now that you’re done configuring your Maven build, set up your Open Liberty to run your test cases by configuring the server.xml configuration file.
Take a look at the server.xml file.
server.xml
link:finish/src/main/liberty/config/server.xml[role=include]The localConnector feature is required by the Arquillian Liberty Managed container to connect to and communicate with the Open Liberty runtime. The servlet feature is required during the deployment of the Arquillian tests in which servlets are created to perform the in-container testing.
Open another command-line session and run the configure-arquillian goal from the start directory to integrate Arquillian and the Arquillian Liberty managed and remote containers with your existing project.
mvn liberty:configure-arquillianBecause you started Open Liberty in dev mode, all the changes were automatically picked up. You can run the tests by pressing the enter/return key from the command-line session where you started dev mode. Look for the following output:
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running it.io.openliberty.guides.system.SystemArquillianIT
...
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.133 s - in it.io.openliberty.guides.system.SystemArquillianIT
[INFO] Running it.io.openliberty.guides.inventory.InventoryArquillianIT
...
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.297 s - in it.io.openliberty.guides.
...
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
...It’s now time to build and run your Arquillian tests outside of dev mode. Exit dev mode by pressing CTRL+C in the command-line session where you ran Liberty in the previous section.
Run the Maven command to package the application. Then, run the Liberty Maven Plugin goals to create the Liberty instance, install the features, and deploy the application to the instance. The configure-arquillian goal configures your Arquillian container. You can learn more about this goal in the configure-arquillian goal documentation.
mvn clean package
mvn liberty:create liberty:install-feature
mvn liberty:configure-arquillianNow, you can run your Arquillian tests with the Maven integration-test goal:
mvn failsafe:integration-testIn the test output, you can see that the Liberty instance launched, and that the web archive, arquillian-managed, started as an application in the instance. You can also see that the tests are running and that the results are reported.
After the tests stop running, the test application is automatically undeployed and the instance shuts down. You should then get a message indicating that the build and tests are successful.
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running it.io.openliberty.guides.system.SystemArquillianIT
...
[AUDIT ] CWWKE0001I: The server defaultServer has been launched.
[AUDIT ] CWWKG0093A: Processing configuration drop-ins resource: guide-arquillian-managed/finish/target/liberty/wlp/usr/servers/defaultServer/configDropins/overrides/liberty-plugin-variable-config.xml
[INFO ] CWWKE0002I: The kernel started after 0.854 seconds
[INFO ] CWWKF0007I: Feature update started.
[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.
[INFO ] Aries Blueprint packages not available. So namespaces will not be registered
[INFO ] CWWKZ0018I: Starting application guide-arquillian-managed.
...
[INFO ] SRVE0169I: Loading Web Module: guide-arquillian-managed.
[INFO ] SRVE0250I: Web Module guide-arquillian-managed has been bound to default_host.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://localhost:9080/
[INFO ] SESN0176I: A new session context will be created for application key default_host/
[INFO ] SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation.
[AUDIT ] CWWKZ0001I: Application guide-arquillian-managed started in 1.126 seconds.
[INFO ] CWWKO0219I: TCP Channel defaultHttpEndpoint has been started and is now listening for requests on host localhost (IPv4: 127.0.0.1) port 9080.
[AUDIT ] CWWKF0012I: The server installed the following features: [cdi-2.0, jaxrs-2.1, jaxrsClient-2.1, jndi-1.0, jsonp-1.1, localConnector-1.0, mpConfig-1.3, servlet-4.0].
[INFO ] CWWKF0008I: Feature update completed in 2.321 seconds.
[AUDIT ] CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 3.175 seconds.
[INFO ] CWWKZ0018I: Starting application arquillian-managed.
...
[INFO ] SRVE0169I: Loading Web Module: arquillian-managed.
[INFO ] SRVE0250I: Web Module arquillian-managed has been bound to default_host.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://localhost:9080/arquillian-managed/
...
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.133 s - in it.io.openliberty.guides.system.SystemArquillianIT
[INFO] Running it.io.openliberty.guides.inventory.InventoryArquillianIT
[INFO ] CWWKZ0018I: Starting application arquillian-managed.
[INFO ] CWWKZ0136I: The arquillian-managed application is using the archive file at the guide-arquillian-managed/finish/target/liberty/wlp/usr/servers/defaultServer/dropins/arquillian-managed.war location.
[INFO ] SRVE0169I: Loading Web Module: arquillian-managed.
[INFO ] SRVE0250I: Web Module arquillian-managed has been bound to default_host.
...
[INFO ] Setting the server's publish address to be /inventory/
[INFO ] SRVE0242I: [arquillian-managed] [/arquillian-managed] [io.openliberty.guides.inventory.InventoryApplication]: Initialization successful.
[INFO ] Setting the server's publish address to be /system/
[INFO ] SRVE0242I: [arquillian-managed] [/arquillian-managed] [io.openliberty.guides.system.SystemApplication]: Initialization successful.
[INFO ] SRVE0242I: [arquillian-managed] [/arquillian-managed] [ArquillianServletRunner]: Initialization successful.
[AUDIT ] CWWKT0017I: Web application removed (default_host): http://localhost:9080/arquillian-managed/
[INFO ] SRVE0253I: [arquillian-managed] [/arquillian-managed] [ArquillianServletRunner]: Destroy successful.
[INFO ] SRVE0253I: [arquillian-managed] [/arquillian-managed] [io.openliberty.guides.inventory.InventoryApplication]: Destroy successful.
[AUDIT ] CWWKZ0009I: The application arquillian-managed has stopped successfully.
[INFO ] SRVE9103I: A configuration file for a web server plugin was automatically generated for this server at guide-arquillian-managed/finish/target/liberty/wlp/usr/servers/defaultServer/logs/state/plugin-cfg.xml.
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.297 s - in it.io.openliberty.guides.inventory.InventoryArquillianIT
...
Stopping server defaultServer.
...
Server defaultServer stopped.
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.018 s
[INFO] Finished at: 2020-06-23T12:40:32-04:00
[INFO] ------------------------------------------------------------------------You just built some functional and integration tests with the Arquillian managed container and ran the tests for your microservices on Open Liberty.
Try one of the related guides to learn more about the technologies that you come across in this guide.