Generate Tests From Business Logic
Generates scenario tests, rule tests, edge case tests, state transition tests, and billing tests from trusted business logic. Use when creating test suites from BL, ensuring BL coverage, or turning requirements into verifiable tests.
Install
npx skills add meirm/reverse-engineering-skill --skill generate-tests-from-business-logicgit clone --depth 1 https://github.com/meirm/reverse-engineering-skill.git /tmp/reverse-engineering-skill
mkdir -p ~/.claude/skills
cp -r /tmp/reverse-engineering-skill/skills/generate-tests-from-business-logic ~/.claude/skills/generate-tests-from-business-logicPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Generating Tests from Business Logic **Project-agnostic.** Use `BDD/project_config.yaml` for terminology and code paths when present; write tests in the project's test framework and structure (see **tailor-bdd-skills-for-project**). ## Purpose Transform trusted business logic into a comprehensive test suite that continuously verifies implementation against business behavior. This is the BL enforcement skill. ## Prerequisites - Refined business logic document (use `refine-business-logic-for-implementation` first) - Understanding of the project's testing framework (pytest, behave, etc.) - Knowledge of the project structure ## Instructions ### Step 1: Parse the Business Logic Read the refined BL document and identify: ```bash cat path/to/refined_bl_document.md ``` Extract: - All business rules (validation, billing, workflows) - State machine definitions (states and transitions) - Decision tables - Invariants - Error handling rules - Billing/credit rules ### Step 2: Classify Test Types Organize tests into these categories: **A. Rule Tests** - Verify individual business rules **B. Scenario Tests** - Verify end-to-end workflows **C. State Transition Tests** - Verify state machine correctness **D. Edge Case Tests** - Verify boundary conditions **E. Billing Tests** - Verify credit operations **F. Regression Tests** - Verify past bugs don't recur ### Step 3: Generate Rule Coverage Tests For each decision rule, generate three tests:
Details
- Skill name
generate-tests-from-business-logic- Repository
- meirm/reverse-engineering-skill
- Path
skills/generate-tests-from-business-logic/SKILL.md- License
- MIT
- Repo updated
- 2 October 2026
FAQ
What does the Generate Tests From Business Logic skill do?
Generates scenario tests, rule tests, edge case tests, state transition tests, and billing tests from trusted business logic. Use when creating test suites from BL, ensuring BL coverage, or turning requirements into verifiable tests.
How do I install the Generate Tests From Business Logic skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add meirm/reverse-engineering-skill --skill generate-tests-from-business-logic. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Generate Tests From Business Logic popular?
It lives in meirm/reverse-engineering-skill, which has 47 GitHub stars and 7 forks.
Related skills
Analyze Business Logic Gaps
47meirm/reverse-engineering-skill
Identifies missing, vague, underspecified, or contradictory business logic within BL documents. Finds incomplete edge cases, missing state transitions, ambiguous terminology, and weak billing rules. Use when reviewing business logic quality, hardening requirements, or preparing BL for implementation.
Bdd Orchestrator
47meirm/reverse-engineering-skill
Orchestrates the full BDD workflow from code to trustworthy business logic — extraction, validation, gap analysis, refinement, acceptance criteria, and test generation. Use when the user requests comprehensive analysis like "understand [feature] from code", "analyze [domain] end-to-end", or "prepare [feature] for implementation or sprint planning", coordinating the other BDD skills step by step.
Derive Acceptance Criteria From Business Logic
47meirm/reverse-engineering-skill
Converts trusted business logic into product-owner-grade acceptance criteria and developer-ready tasks using Given/When/Then scenarios. Use when creating user stories, preparing for sprints, or turning BL into executable requirements.
Vibe Testing
24knot0-com/vibe-testing
This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.
Timovi QA Engineer
49theminimalcreator/timovi
QA Engineer for the Timovi project. Validates framework completeness and testability with Given/When/Then criteria, edge cases, and quality risks. Use when planning tests for the framework, defining acceptance criteria for pipeline phases, analyzing edge cases in state transitions, or reviewing framework quality.
Game Web2d Specialist
57AlterLab-IEU/AlterLab_GameForge
Builds 2D browser games with Phaser 4 (primary), PixiJS 8, Kaplay, Excalibur or LittleJS: framework choice, Phaser scenes, Arcade or Matter physics, Tiled/LDtk tilemaps, atlases, pixel-art scaling, Phaser 3 to 4 migration and Playwright checks. Use for "Phaser", "PixiJS", "Kaplay", "2D web game", "tilemap". Not for 3D browser games (use game-threejs-specialist).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.