Integrating Sealights with tests

Here we’re going to explain running tests with Sealights on the boutique app.

As you should know there is a Sealights agent called test runner, it opens or closes the test stages letting the test listener (the agent running on the apps) start or stop tracking lines of code that are run respectively. Also, if we support the testing framework (sometimes even if we don't) at the end of the test stage it sends test report of how many tests ran, for how long, how many succeeded and how many skipped.

For time and simplicity we've decided to run all the tests in one image. The job runs tests one after the other with some wait time between them (to give our backend time to stop the test stage for test stage accuracy).

We're not going to go over the test frameworks, but in our example we cover the following testing frameworks:

Framework

Example

Cucumber (JS)

https://github.com/Sealights/microservices-demo-template/tree/public/integration-tests/Cucumber-js

Cucumber (Java)

https://github.com/Sealights/microservices-demo-template/tree/public/integration-tests/cucumber-framework

Cypress

https://github.com/Sealights/microservices-demo-template/tree/public/integration-tests/cypress

https://github.com/Sealights/microservices-demo-template/tree/public/integration-tests/dotnet-tests/MS-Tests

Nunit

https://github.com/Sealights/microservices-demo-template/tree/public/integration-tests/dotnet-tests/NUnit-Tests