nw-test-organization-conventions

Identify and enforce architecture-aligned test organization for software projects.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-test-organization-conventions-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-test-organization-conventions
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-test-organization-conventions
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-test-organization-conventions-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests are often scattered in ways that obscure architectural boundaries, making it hard to infer system organization from the test tree and causing maintenance and boundary violations.

Core Features & Use Cases

  • Architecture-aware test organization guidance aligned with common patterns such as Hexagonal / Clean Architecture, Vertical Slice, Modular Monolith, Microservices, Event-Driven, CQRS, and Layered approaches.
  • Decision-tree style guidance that maps architectural style to test placement, naming, and boundary tests, enabling a hybrid strategy that scales with project growth.
  • Language-agnostic conventions and fixture organization guidance to improve discoverability, CI speed, and boundary enforcement across teams.

Quick Start

Assess a project's current test layout and generate an architecture-aligned organization plan.

Frequently Asked Questions about nw-test-organization-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize tests for a hexagonal or clean architecture project?

Test organization for hexagonal architecture should map directly to architectural boundaries, placing tests to enforce ports and adapters. This Skill generates a plan aligning unit, integration, and end-to-end tests with your specific structural patterns.

What is the best way to structure tests in a modular monolith to prevent boundary violations?

Structuring tests in a modular monolith requires architecture-aware placement to prevent boundary violations. This Skill provides decision-tree guidance mapping your architectural style to specific test placement and naming conventions.

How do I set up contract tests for microservices and event-driven systems?

Contract tests for microservices and event-driven systems are configured using cross-context testing guidance. This Skill helps define naming conventions and boundary tests to verify interactions between independent services.

Can I use architecture-aligned test organization with a vertical slice architecture?

Yes, architecture-aligned test organization supports vertical slice architecture. The Skill provides language-agnostic conventions and fixture organization guidance tailored to vertical slices and other supported patterns like CQRS.

Does this test organization approach work for CQRS and event-driven patterns?

This test organization approach explicitly works with CQRS and event-driven patterns. It maps these architectural styles to appropriate test placement, naming conventions, and boundary tests to guide teams from planning to CI.

Why should tests be organized by architecture instead of by test type?

Organizing tests by architecture prevents scattered tests that obscure system boundaries and cause maintenance issues. Aligning test trees with your architecture improves discoverability, CI speed, and boundary enforcement across teams.