coldbox-testing-integration

ColdBox integration tests use the BaseTestCase execute() method to run full request cycles, exercising real handlers and WireBox-injected services against an actual database without relying on mocks. You can assert response codes and payloads directly from the renderResults output.

To isolate database state during ColdBox end-to-end testing, use a dedicated test datasource and apply transaction rollback or targeted delete patterns in your setup and teardown methods. This ensures deterministic database cleanup and prevents test data from affecting other tests.

You can test WireBox dependency injection by obtaining actual injected services during the BaseTestCase request cycle. This allows you to verify real persistence and inter-service interactions rather than mocking dependencies.

Yes, you can verify response payloads and HTTP status codes by executing handler and API endpoints via the BaseTestCase execute() method. It returns a renderResults-based response object that allows you to assert specific response codes like 201 and validate the returned data structure.

ColdBox integration testing requires a dedicated test datasource configuration to ensure deterministic database setup and cleanup. This isolates your test data from development or production databases and supports transaction rollback or targeted cleanup patterns.

Transaction rollback provides deterministic database setup and cleanup for ColdBox database testing by reverting changes after each test, whereas mocks bypass real database operations. Using rollback ensures your tests exercise actual persistence layers and inter-service interactions for true end-to-end coverage.