testing-strategies

To set up integration tests without mocking, you run tier 2 and tier 3 tests against real infrastructure using Docker-based test environments. This approach provides realistic validation by interacting directly with actual databases, APIs, and services instead of using mocks.

A 3-tier testing strategy structures validation into unit, integration, and end-to-end testing patterns. It separates tests by scope, using in-memory mocks only for tier 1 unit tests while requiring real infrastructure for tiers 2 and 3.

Yes, you need Docker to run CI/CD integration tests for Kailash apps. The strategy requires Docker-based test environments to provision real infrastructure for running non-mocked tier 2 and tier 3 tests in your pipeline.

You organize test fixtures for end-to-end testing patterns by following documented directory layouts and example test workflows. The strategy provides reference templates to structure your fixtures and test organization for rapid adoption.

You should avoid mocking in your testing strategy for tier 2 integration and tier 3 end-to-end tests. The framework enforces a NO MOCKING policy across these tiers to ensure tests validate against real databases, APIs, and services.