Testing End To End Only¶

Reject end-to-end-only verification for isolated decisions that need fast diagnostic feedback.

Generated example

This page is generated from evaluations/scenarios/testing-end-to-end-only.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¶

Put every rule behind one broad workflow test.
Use test-level ratios as a substitute for risk analysis.

Scenario source¶

schema_version: 0.10.0
id: testing-end-to-end-only
description: Reject end-to-end-only verification for isolated decisions that need
  fast diagnostic feedback.
input:
  skill: testing-strategy
  mode: integration-balanced
  task: Design verification for many pure rules and one external collaboration.
expected:
  active_principles:
  - first-tests
  - test-behaviour-not-implementation
  constrained_principles:
  - test-pyramid
  suppressed_principles: []
forbidden:
- Put every rule behind one broad workflow test.
- Use test-level ratios as a substitute for risk analysis.
principles_under_test:
- first-tests
- test-behaviour-not-implementation
- test-pyramid
- one-logical-behaviour-per-test