Test Tutorial

As there are several dependencies for light-eventuate-4j applications to run, it is a little complicated to test services built on top of light-eventuate-4j compare with other simple services.

In this section, we will walk through the Unit Test, Integration Test and End-to-End Test with real examples so that others can learn what is the difference of each type of test and how to write these test ensure high quality services are produced.

Unit Test is located in /test folder in src and these test cases will have no external dependencies.

Integration Test is located in /integration folder in src and these test cases will have external dependencies.

End-to-End Test is normally locate in light-bot and it will run in an environment that all related services will be running at the same time.

Unit Test

Before reading specific information regarding the Unit Test, please read the general unit test tutorial This section will only focus on the specific information regarding to light-eventuate-4j. There are a lot of modules in light-eventuate-4j and each module has its own JUnit test cases. They are all located in each project’s src/test folder. There might also be a config folder under src/test/resources/ to control how each involved light-4j component behaves. Read More »

Integration Test

Integration tests are located in each sub-project src/integration folder and the filenames are ended with IT instead of Test like Unit Tests. For more information on how to write integration tests in general, please refer to Integration Test Tutorial. As light-eventuate-4j framework contains a lot of moving parts and depends on Kafka, Zookeeper, Mysql and CDC server to run, most test cases in the project are actually integration tests instead of unit tests. Read More »

End to End Test

End-to-End test in light-eventuate-4j application is very hard as many components need to work together in order for message to be delivered from one service to another. Also, each service instance must live long enough in order to receive async events. Internally, we have so many services that are built on top of light-eventuate-4j and light-hybrid-4j and we are using light-bot develop task to test them all during the develop branch build. Read More »