Testing

TestBox unit specs for every entity and service, plus integration specs over real HTTP requests.

Testing

CB Genesis ships with a TestBox suite covering every service and entity, plus integration specs that exercise real requests.

Running tests

box testbox run                        # All tests
box testbox run --labels=unit          # Unit tests only
box testbox run --labels=integration   # Integration tests only

Test structure

tests/
├── Application.bx              Virtual ColdBox app (appMapping="/app")
├── runner.bxm                  TestBox CLI runner entry
├── specs/
│   ├── integration/
    │   │   └── MainSpec.bx         Lifecycle events and exception handling
│   └── unit/
│       ├── security/           APIToken, Permission, Role, SecurityService tests
│       └── system/             Setting, User tests
└── resources/
    └── BaseIntegrationSpec.bx  Shared helper for integration tests

The naming convention is one unit spec per entity and one per service, split by domain folder (security, system) - mirroring app/models. Follow the same pairing when you add your own domain.

Writing an integration spec

Integration specs extend tests.resources.BaseIntegrationSpec, which wires up appMapping="/app" so paths resolve exactly like production:

component extends="tests.resources.BaseIntegrationSpec" {

    function run(){
        describe( "Registration", () => {
            it( "renders the registration form", () => {
                var event = execute( event = "Auth.register", renderResults = true );
                expect( event.getValue( "cbox_rendered_content" ) ).toInclude( "register" );
            } );
        } );
    }

}

The checked-in suite contains unit coverage for the security and system entities/services plus the Main integration spec. Add integration coverage for new routes and handlers as you build them; a feature is not covered merely because its service has a unit spec.