Apache Camel - testing
To create integration tests for your Apache Camel routes, you need to create service tests by extending the AbstractGenesisTestSupport class and specifying the relevant application-name-camel.kts file as the scriptFileName.
To create integration tests for your Apache Camel routes, you need to create service tests by extending the AbstractGenesisTestSupport class and specifying the relevant application-name-camel.kts file as the scriptFileName.
There are three easy ways of testing components in your application:
Integration testing
Integration testing
GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).
You can not programmatically test integrations configured using the GenesisToDb module. However,
GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).
lerna
The foundation-testing package is a comprehensive framework for implementing End-to-End (E2E) testing. Use it to ensure that your Genesis Web Application provides a seamless user experience by testing workflows and user interactions across various scenarios.
Whichever component of your application you are testing, there is a simple set of tools that you can use. This page looks at those tools and the dependencies that you must declare before you can start automated testing.
You can use the foundation-testing package to ensure that your Genesis Web Application provides a seamless user experience by testing components, functions and user interactions across various scenarios.
GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).
Database and service tests
GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).
The REST Endpoints created by the Genesis low-code platform reflect your application's business logic. These endpoints can be configured through the Genesis Router.
Integration testing
Integration testing
Unit testing does not require a database or the running of a Genesis service. So, as you define your application, each component should be unit-tested according to standard best practice.