16 docs tagged with "testing"

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.

Component testing

There are three easy ways of testing components in your application:

Consolidator - testing

Integration testing

Custom endpoints - testing

Integration testing

Data Pipeline - testing

To test a data pipeline you need:

Data Server - testing

Integration testing

DB streaming out - testing

You can not programmatically test integrations configured using the GenesisToDb module. However,

Evaluator - testing

To see a working example of both static and dynamic Evaluators, please go to the Setting Genesis Rules page, where there is a working example of both.

Event Handler - testing

Integration testing

Foundation Testing

lerna

Integration testing

Database and service tests

Request Server - testing

Integration testing

REST endpoints - testing

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.

State Machine - testing

Integration testing

Testing Java Event Handlers

Integration testing

Unit 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.