Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-test-organization-conventions
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
Passed 20 of 22 test cases with the skill, and 14 of 22 without it.
and 6 more in the full report
6 fixed14 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a Python backend adhering to ports and adapters (Hexagonal Architecture) and testing with pytest. Please design a detailed test directory folder structure for our project, explaining how to organize unit, integration, acceptance, and E2E suites, as well as where pytest conftest.py files should be located for proper fixture scoping.
| Checked | Without skill | With skill |
|---|---|---|
| Uses a test-type-first top-level layout with unit, integration, acceptance, and e2e subdirectories under tests/ | Passed | Passed |
| Places port contract tests inside tests/integration/ | Missed | Passed |
| Places conftest.py files hierarchically at the root tests/ and within individual test tier subdirectories | Passed | Passed |
| Nests domain features inside test-type subdirectories instead of creating top-level layer directories like domain/ or adapters/ | Passed | Passed |
The instructions your model reads when the skill loads.
Test directory structure encodes architectural boundaries. If a developer cannot infer the architecture from the test tree alone, the organization is wrong.
What is the project's architectural style?
|
+-- Hexagonal / Clean Architecture
| --> Test-type-first: tests/{unit,integration,acceptance,e2e}/
| --> Domain concepts nested within each type
| --> Port contract tests in tests/integration/
|
+-- Vertical Slice
| --> Co-located: features/{slice}/tests/
| --> Cross-slice tests in top-level tests/cross_feature/
|
+-- Modular Monolith
| --> Module-first: tests/modules/{module}/{unit,integration}/
| --> Architecture tests per module (dependency rule enforcement)
| --> Inter-module tests in tests/inter_module/
|
+-- Microservices
| --> Per-service test tree: {service}/tests/{unit,integration,component,contract}/
| --> Contract tests: consumer writes in own repo, provider verifies in own repo
| --> Cross-service E2E in separate project: e2e-tests/
|
+-- Event-Driven
| --> Test-type-first with event-specific categories
| --> Unique: schema contract tests, idempotency tests, saga compensation tests
|
+-- CQRS
| --> Command/Query split within each test type
| --> Unique: projection tests (rebuild + idempotency)
|
+-- Layered (N-Tier)
| --> Mirror source: tests mirror src layer hierarchy
test cases passed, vs 14 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.