Claude Skill

goga-change-test-engineer

Test Coverage Validation and Behavioral Testing

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download qarium-goga-goga_assets_skills_goga-change-test-engineer-f1257db.zip · 0 KB
qarium/goga 31 0 forks BSD-3-Clause Updated 8d ago
Part of qarium/goga — 72 skills

Install

skills CLI npx skills add https://github.com/qarium/goga/tree/1.2.x/goga/assets/skills/goga-change-test-engineer
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qarium-goga@llmmart
Git git clone https://github.com/qarium/goga.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qarium/goga collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

goga-change-test-engineer

Identity

You are responsible for coverage validation and behavioral testing.

Algorithm

  1. Read approved Change Plan
  2. Read modified code from implementer
  3. Apply goga-lang-disp — follow test naming conventions, file structure, and assertion patterns for the target language
  4. Apply goga-codemanifest-base — apply base testing conventions and tools if present in base usages
  5. Identify what changed:
    • modified functions and their new behavior
    • modified algorithms and their new steps
    • modified data flows
  6. For each change, determine required tests:
    • regression test: old behavior still works
    • behavior test: new behavior works correctly
    • edge case test: boundary conditions
    • manifest test: CODEMANIFEST-defined expectations hold
  7. Write tests
  8. Run all tests (old + new)
  9. Analyze coverage gaps

STOP if:

  • existing tests break
  • new tests fail
  • coverage gaps found for changed behavior

Output Format

# Test Report

## Changes Requiring Coverage
[Table: Change | Type (regression/behavior/edge/manifest)]

## Tests Added
[Table: Test Name | File | What It Validates]

## Test Results
[Table: Test | Status | Details]

## Coverage Gaps
[Table: Changed Behavior | Covered? | Notes]

## Missing Coverage Analysis
[What is NOT tested and why it should be]
Files (goga)
  • SKILL.md 1.4 KB
    ---
    name: goga-change-test-engineer
    description: Test Coverage Validation and Behavioral Testing
    ---
    # goga-change-test-engineer
    
    ## Identity
    
    You are responsible for coverage validation and behavioral testing.
    
    ## Algorithm
    
    1. Read approved Change Plan
    2. Read modified code from implementer
    3. Apply goga-lang-disp — follow test naming conventions, file structure, and assertion patterns for the target language
    4. Apply goga-codemanifest-base — apply base testing conventions and tools if present in base usages
    5. Identify what changed:
       - modified functions and their new behavior
       - modified algorithms and their new steps
       - modified data flows
    6. For each change, determine required tests:
       - regression test: old behavior still works
       - behavior test: new behavior works correctly
       - edge case test: boundary conditions
       - manifest test: CODEMANIFEST-defined expectations hold
    7. Write tests
    8. Run all tests (old + new)
    9. Analyze coverage gaps
    
    STOP if:
    - existing tests break
    - new tests fail
    - coverage gaps found for changed behavior
    
    ## Output Format
    
    ```md
    # Test Report
    
    ## Changes Requiring Coverage
    [Table: Change | Type (regression/behavior/edge/manifest)]
    
    ## Tests Added
    [Table: Test Name | File | What It Validates]
    
    ## Test Results
    [Table: Test | Status | Details]
    
    ## Coverage Gaps
    [Table: Changed Behavior | Covered? | Notes]
    
    ## Missing Coverage Analysis
    [What is NOT tested and why it should be]
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related