Testing Characterization Change¶

Capture relied-upon legacy behavior before restructuring while allowing an explicit defect correction.

Generated example

This page is generated from evaluations/scenarios/testing-characterization-change.yaml. The scenario YAML remains the executable source of truth.

Request¶

Repository evidence¶

No repository signals.

Expected resolution¶

Resolution layer	Expected
Profile	—
Modifiers	—
Language adapters	—
Framework adapters	—

Normalized context¶

{}

Skill modes¶

None.

Conflict decisions¶

None.

Significant decisions¶

None.

Principles under test¶

Forbidden outcomes¶

Refactor before observing current outcomes.
Preserve the confirmed defect as permanent behavior.

Scenario source¶

schema_version: 0.10.0
id: testing-characterization-change
description: Capture relied-upon legacy behavior before restructuring while allowing
  an explicit defect correction.
input:
  skill: testing-strategy
  mode: characterization-first
  task: Refactor an uncertain workflow and correct one requirement-confirmed defect.
expected:
  active_principles:
  - test-behaviour-not-implementation
  - first-tests
  - chestertons-fence
  constrained_principles:
  - test-driven-development
  - red-green-refactor
  suppressed_principles: []
forbidden:
- Refactor before observing current outcomes.
- Preserve the confirmed defect as permanent behavior.
principles_under_test:
- test-behaviour-not-implementation
- first-tests
- chestertons-fence
- test-driven-development