coldbox-testing-base-classes

Choose your ColdBox testing base class by matching test goals: BaseTestCase for integration, BaseHandlerTest for isolated handlers, BaseModelTest for models, and BaseInterceptorTest for interceptors. This alignment accelerates test development by providing pre-wired setups and mocks for each specific scenario.

The standard ColdBox testing harness structure requires a tests directory containing Application.cfc, resources, and specs subdirectories. This conventional layout provides the necessary mappings, fixtures, and configurations to support integration, handler, model, and interceptor testing scenarios.

Yes, you can use BaseHandlerTest for isolated handler testing and BaseInterceptorTest for isolated interceptor testing in ColdBox. These base classes provide pre-wired setups and mocks specifically designed to test handlers and interceptors independently without loading the entire framework.

The best way to structure ColdBox test specs, mappings, and fixtures is to extend the appropriate base test class and follow the conventional harness layout. Place test specifications in the tests/specs directory, configure mappings in tests/Application.cfc, and store fixtures in tests/resources for standardized test development.

Yes, knowledge of common ColdBox annotations is required to set up a test harness effectively. The harness setup uses standard annotations to configure pre-wired setups, mocks, and mappings that enable proper integration, handler, model, and interceptor testing scenarios.

ColdBox tests fail when extending the wrong base test class for the intended test type. Ensure you extend BaseTestCase for integration, BaseHandlerTest for handlers, BaseModelTest for models, or BaseInterceptorTest for interceptors, and verify the standard harness layout is properly configured.