The Standard Testing

Enforce standardized unit, validation, and exception tests across application layers.

1|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/NHSISL/LondonFhirService --skill the-standard-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: The Standard Testing
Source: https://github.com/NHSISL/LondonFhirService/tree/main/.agents/skills/the-standard-testing
Command: npx skills add https://github.com/NHSISL/LondonFhirService --skill the-standard-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Standard Testing provides a comprehensive framework for enforcing TDD discipline, validation testing, exception mapping, controller acceptance tests, and UI component testing across foundational, processing, orchestration, and UI layers.

Core Features & Use Cases

  • Establishes a standardized testing lifecycle, including happy-path, structural/validation, and exception tests.
  • Guides test structure with separate Logic, Validations, and Exceptions files and strict naming and verification conventions.
  • Ensures consistent logging, verification of broker calls, and state isolation through deep cloning and randomized test data.

Quick Start

Create tests that follow the Standard's three-axis structure, verify exact broker calls, and log errors for failed cases.

Frequently Asked Questions about The Standard Testing

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

FAQPage Schema
How do I enforce consistent TDD discipline and unit test structure across different application layers?

Enforce TDD discipline by applying a standardized testing lifecycle across foundation, processing, orchestration, and UI layers, requiring separate Logic, Validations, and Exceptions files with strict naming conventions.

What is the best way to structure exception mapping and validation tests for governance compliance?

Structure exception mapping and validation tests using a three-axis framework that isolates exceptions, verifies state through deep cloning, and logs errors to fulfill governance requirements for error localization.

How do I verify exact broker calls and ensure state isolation during unit testing?

Verify exact broker calls and ensure state isolation during unit testing by utilizing deep cloning techniques and randomized test data, enforcing consistent logging and verification across all processing layers.

Can I use a standardized testing framework for both backend orchestration logic and UI components?

Yes, this testing framework applies to both backend orchestration logic and UI components, enforcing a unified structure for controller acceptance tests, exception mapping, and validation testing across all layers.

Why does my testing discipline fail governance requirements for error localization and logging?

Testing discipline fails governance requirements when it lacks standardized exception mapping, consistent logging for failed cases, and strict verification of broker calls, which are enforced by a rigorous testing lifecycle.