skills.rest
apolosan
apolosanCOMMUNITY
Explore all skills by this author →
GitHub

up-tdd

Automate creation of immutable unit, integration, and E2E test batteries before writing UP code.

3|Updated Mar 31, 2026
Search Tags:#testing#tdd#unit-testing#integration-testing#quality-assurance#up#test-battery
One-click install
npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: up-tdd
Source: https://github.com/apolosan/unified_process_pi_extension/tree/main/skills/up-tdd
Command: npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams define a complete, immutable test battery before writing UP code, ensuring contracts, use cases, and non-functional requirements are tested from day one.

Core Features & Use Cases

  • Defines a comprehensive test battery across unit, integration, and end-to-end levels to cover UP artifacts.
  • Enforces immutability and formal change control for test specifications.
  • Provides a structured workflow (5W2H, inventory review, and TDD plan templates) guiding CI/CD integration.
  • Supports stakeholder-suggested tests with traceable logging and immutability rules.

Quick Start

Lock the TDD plan and generate the full UP test battery according to the templates before writing any code.

Frequently Asked Questions about up-tdd

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

FAQPage Schema
How do I define a complete unit, integration, and E2E test battery before writing code?▼

Define a complete test battery upfront by applying structured 5W2H analysis and artifact review to map all unit, integration, and E2E tests before coding begins. This ensures contracts, use cases, and non-functional requirements are tested from day one.

What is an immutable test specification and how does it enforce quality assurance?▼

An immutable test specification is a locked, unchangeable test definition that enforces quality assurance through formal change control. It ensures stakeholder traceability and prevents undocumented modifications to unit, integration, and E2E test criteria.

How do I trace stakeholder-suggested tests back to original requirements?▼

Trace stakeholder-suggested tests using structured logging and immutability rules that map each test to specific requirements. This formal change-control documentation maintains traceability across all unit, integration, and end-to-end test levels.

What is the best way to lock TDD plans across construction and transition phases?▼

The best way to lock TDD plans is to generate the full test battery according to structured templates before writing any code. This enforces immutability, meets coverage targets, and guides 5W2H analysis across construction and transition phases.

Related Skills

Explore More Software Engineering Skills→
apolosanapolosan
3

up-5w2h

Generate context-specific 5W2H questions for Unified Process activities.

Community
Intermediate
bobmatnycbobmatnyc
68

wordpress-testing-qa

Run PHPUnit and WP_Mock tests for WordPress plugins and themes.

Community
Intermediate
hopeoverturehopeoverture
6

github-actions-ci-workflow

Generate GitHub Actions CI/CD workflows for web apps with lint, test, build, and deploy pipelines.

Community
Advanced
thechandanbhagatthechandanbhagat
8

test

Generate pytest and Jest unit tests, integration tests, and mock data.

Community
Basic