testing-conventions

Define deterministic testing conventions for financial verification suites.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/H-Analytics --skill testing-conventions-norfolk-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-conventions
Source: https://github.com/Norfolk-Group/H-Analytics/tree/main/.claude/archive/agents-skills-snapshot/testing-conventions
Command: npx skills add https://github.com/Norfolk-Group/H-Analytics --skill testing-conventions-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear conventions and patterns to remove ambiguity and flakiness from the financial verification test suite so that all calculations are deterministic, traceable, and auditable across the codebase.

Core Features & Use Cases

  • Golden Test Pattern: Hand-derived reference scenarios with fixed inputs and penny-level assertions to validate core calculators.
  • Proof Scenarios: Five structural scenarios that exercise every financial path (cash purchase, financed purchase, cash→refinance, portfolio aggregate, consolidated eliminations) to prove GAAP identities.
  • Reconciliation & Artifacts: Automated generation of JSON and Markdown reconciliation artifacts that document sources & uses, NOI→FCF bridges, and debt reconciliation with severity-coded audit opinions.
  • Hardcoded Detection & Data Integrity: Scans for magic numbers, enforces safe constants, and validates database ownership and uniqueness constraints.
  • Fixture Factory & Verify Pipeline: Mandates use of shared fixture factories for test inputs and an 8-phase npm run verify pipeline that must result in an UNQUALIFIED opinion before merge.

Quick Start

Run the full verification pipeline with npm run verify to generate reconciliation artifacts and confirm an UNQUALIFIED audit opinion.

Frequently Asked Questions about testing-conventions

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

FAQPage Schema
How do I ensure deterministic and auditable financial verification in my test suite?▼

Financial verification ensures deterministic and auditable results by applying golden tests with hand-derived values, fixture factories, and an 8-phase verify pipeline that outputs reconciliation artifacts with severity-coded audit opinions.

What is a golden test pattern for finance engine calculations?▼

A golden test pattern validates core calculators using fixed inputs and hand-derived expected values with penny-level assertions, ensuring traceable and repeatable results for financial models.

How do I generate reconciliation artifacts for GAAP identities and debt bridges?▼

Generate JSON and Markdown reconciliation artifacts by running an 8-phase verify pipeline that documents NOI→FCF bridges, debt reconciliation, and sources & uses with severity-coded audit opinions.

Can I use fixture factories to eliminate hardcoded numbers in financial test scenarios?▼

Fixture factories mandate shared test inputs while hardcoded-detection scans for magic numbers and enforces safe constants, ensuring data integrity across proof scenarios and financial verification paths.

What are the structural proof scenarios required for hospitality financial models?▼

Five structural proof scenarios exercise every financial path: cash purchase, financed purchase, cash→refinance, portfolio aggregate, and consolidated eliminations, proving GAAP identities across the codebase.

Why does my npm run verify pipeline require an UNQUALIFIED audit opinion before merge?▼

The verify pipeline requires an UNQUALIFIED audit opinion before merge to confirm all golden tests, proof scenarios, reconciliation reports, and hardcoded-detection checks pass with penny-level precision.