analyzing-integration-tests

You can generate integration test documentation by analyzing tests that verify component interactions and database access, outputting structured markdown files into a docs/unwind/layers/integration-tests/ directory with an index and per-type sections.

The best way to document test coverage for external service integration is to run a structured analysis that automatically produces an index and per-type section files in a dedicated directory, improving visibility across component interactions.

Yes, you can use incremental writing to analyze integration tests in large codebases. This approach supports stepwise analysis and progressive disclosure, allowing you to generate documentation progressively without processing everything at once.

No specific testing frameworks are required. The analysis is applicable to any projects that verify component interactions, database access, and external service integration, operating without dependencies to produce structured documentation.

To structure integration test analysis output for machine readability, the tool generates a docs/unwind/layers/integration-tests/ directory containing an index.md file alongside per-type section files, ensuring a standardized and parseable documentation layout.

You need to produce structured documentation for integration tests when you add or modify tests verifying component interactions or database access, ensuring test coverage visibility is maintained through an automatically generated documented layer.