ihabkhaled Targeted Testing
Core principle
Test from smallest relevant proof to required global gate; schedule quality intelligently without lowering it.
Procedure
- Map the change to its closest unit or focused test.
- Run the failing or targeted proof first.
- Expand to relevant integration and E2E only as risk requires.
- Run lint, typecheck, build, and repository gates at the appropriate checkpoint.
- Classify failures as introduced, pre-existing, environmental, flaky, or unknown.
- Record what each command proves.
Required output
Test sequence, results, failure classification, and remaining mandatory gate.
Limits
Do not rerun full suites after every small edit unless policy requires it.
Common mistakes
Do not skip security or regression gates, or run commands without knowing the evidence sought.
Stop condition
Stop when the current checkpoint has sufficient proof and continue to the next unmet requirement.