testing-strategy — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited testing-strategy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill enforces a complete, evidence-based testing strategy — preventing premature sign-off, skipped test levels, and UAT conducted without proper test case coverage.
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip unit testing and jump to E2E | "SAP standard code doesn't need unit tests" | Custom ABAP, BAdIs, and enhancements absolutely need unit tests. Bugs caught at unit level cost 10x less than E2E bugs. | Checklist Step 1: Unit test coverage is mandatory for all custom code. |
| Run UAT without a formal test case library | "The business users know the process" | Business users test what they remember, not what the system must do. Coverage gaps guarantee post-go-live defects. | Hard Gate: UAT cannot begin without signed-off test case library. |
| Use production data directly in testing | "It's the most realistic data" | GDPR violation. Also — prod data corrupted by test activity is a catastrophic incident. | Iron Law 3: Anonymized data or synthetic data only. No exceptions. |
| Mark defects closed based on developer word | "The developer has fixed it in the system" | Configuration drift, transport errors, and regression mean developer confidence ≠ working system. | Iron Law 4: All defects require documented retest before closure. |
| Skip performance testing because "SAP handles it" | "SAP is enterprise-grade, it scales" | SAP scales. Your custom code, Z-tables, and integration points may not. Volume testing is mandatory. | Checklist Step 5: Performance test mandatory for all high-volume processes. |
| Report test completion without defect resolution | "We've run all the test cases" | Running tests and passing tests are different things. Open critical defects block sign-off. | Verification: Zero open P1/P2 defects required for sign-off. |
Watch for these phrases in your own reasoning — each signals an Iron Law violation:
<HARD-GATE> UAT sign-off CANNOT be granted until:
If any of these conditions is unmet, the status is NOT signed off. Do not represent it as ready. </HARD-GATE>
PROJECT: [Name]
DATE: [Date]
VERSION: [Version]
TEST PYRAMID SCOPE
------------------
Unit Testing: [In scope / Out of scope] — [Rationale]
Integration Testing: [In scope / Out of scope] — [Rationale]
E2E Testing: [In scope / Out of scope] — [Rationale]
UAT: [In scope] — [Business users, dates, location]
Performance Testing: [In scope / Out of scope] — [Rationale]
Regression Testing: [In scope] — [Trigger conditions]
TEST DATA STRATEGY
------------------
Source: [Origin of test data]
Anonymization: [Tool / approach]
Volume: [Record counts per entity]
AUTOMATION SCOPE
----------------
Tool: [Tosca / Selenium / SAP TAO / None]
Automated scenarios: [List]
Manual scenarios: [List]
DEFECT MANAGEMENT
-----------------
Tool: [JIRA / Azure DevOps / SAP Solution Manager]
Priority definitions: P1=[definition] P2=[definition] P3=[definition] P4=[definition]
SLA: P1=[hours] P2=[hours] P3=[hours] P4=[hours]
SIGN-OFF AUTHORITY
------------------
UAT sign-off: [Name, role]
Go-live approval: [Name, role]| ID | Module | Process | Test Case | Type | Priority | Status | Tester | Pass/Fail | Defect Ref |
|-------|--------|-----------------|------------------------------|----------|----------|---------|--------|-----------|------------|
| TC001 | FI | Invoice Posting | Post vendor invoice — valid | Positive | P1 | Pending | [Name] | | |
| TC002 | FI | Invoice Posting | Post invoice — missing field | Negative | P1 | Pending | [Name] | | |
| TC003 | MM | Purchase Order | Create PO — standard | Positive | P1 | Pending | [Name] | | |
| TC004 | MM | Purchase Order | Create PO — blocked vendor | Negative | P2 | Pending | [Name] | | |This skill is complete ONLY when ALL of the following are true:
Evidence required: Test strategy document, test case matrix with pass/fail status, defect log, performance test report, signed UAT sign-off form.
If any item above is unchecked, this skill is NOT complete. Do not claim sign-off readiness.
After completing this skill, invoke: data-migration Conditions for handoff: Testing strategy signed off and UAT complete. Data migration execution requires its own testing (reconciliation, trial run) — invoke the data-migration skill next.
go-live-readiness — Testing sign-off is one input to the go/no-go matrix; invoke after this skillcutover-planning — Test completion gates cutover executiondevelopment-workflow — Unit test standards for custom developmentsap-test-designer agent — Use for automated test case generation from process specs~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.