# Goga Change Test Engineer

> Test Coverage Validation and Behavioral Testing

- Skill: `qarium/goga-change-test-engineer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add qarium/goga-change-test-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qarium/goga-change-test-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: qarium (https://skillmd.com/u/qarium)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qarium/goga-change-test-engineer

---

# 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]
```