coldbox-testing-interceptor

To unit test ColdBox interceptors in isolation, extend BaseInterceptorTest to access pre-wired mock helpers like mockController and mockRequestService, avoiding a full application boot. You then call interception points directly on the interceptor instance with a mocked request context.

Mock the request context and logger using the pre-wired mockRequestService, mockLogger, and mockLogBox helpers provided by the BaseInterceptorTest harness. You pass the mocked request context directly when invoking interception points.

Set configProperties before calling super.setup() in your unit test's setup method. This ensures the interceptor initializes with the correct configuration properties before you inject any additional mock collaborators.

Yes, you can call custom announce points and onException handlers directly on variables.interceptor with a mocked request context. This direct invocation lets you assert specific behavior and side effects for each interception point.

The best way to inject mock collaborators is via prepareMock or property injection after setting configProperties. This allows you to simulate dependencies like the controller, request service, logger, and flash scope before asserting interactions.

Yes, TestBox works seamlessly with the BaseInterceptorTest harness, which supplies ready-to-use mockController and mockFlash objects. These pre-wired mocks reduce setup overhead and flakiness when testing ColdBox interceptors.