nw-test-design-mandates

Enforce acceptance-test design mandates for boundary enforcement, business language, and user journeys.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mandates for acceptance-test design ensure tests are driven by external entry points, written in business language, and cover complete user journeys with scalable patterns like walking skeletons.

Core Features & Use Cases

  • Enforce boundary testing by requiring driving ports as entry points
  • Promote business-language abstraction across test steps
  • Ensure complete user journeys with observable business value
  • Include Walking Skeleton guidance to balance coverage and speed

Quick Start

Review the three mandates and apply them to your acceptance tests to verify boundary testing, business-language abstraction, and complete user journeys.

Frequently Asked Questions about nw-test-design-mandates

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

FAQPage Schema
How do I enforce boundary testing and business language in acceptance tests?

You can enforce boundary testing and business language in acceptance tests by applying design mandates during peer review. This requires tests to use driving ports as entry points and abstract test steps into business language.

What is a walking skeleton in acceptance test design?

A walking skeleton is an acceptance test design pattern that balances coverage and speed. It ensures complete user journeys with observable business value while maintaining scalable test structures across features.

How do I verify complete user journeys during peer review?

You verify complete user journeys during peer review by checking that acceptance tests cover end-to-end scenarios with observable business value. Design mandates require evidence collection to validate this coverage.

Does this acceptance test design approach require external entry points?

Yes, this acceptance test design approach requires external entry points. Boundary enforcement mandates specify that tests must be driven by driving ports to ensure proper boundary testing.

What are the mandates for acceptance test structure and readability?

The mandates for acceptance test structure and readability require boundary enforcement, business language abstraction, and complete user journeys. Compliance is verified through evidence collection during peer review.

When should I not use design mandates for acceptance tests?

Design mandates for acceptance tests may not suit projects lacking driving ports or clear business language requirements. They apply specifically to scenarios validating test structure, readability, and end-to-end coverage.