Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add efeumutaslan/SAP-SKILLS --skill sap-testing-qualitygit clone --depth 1 https://github.com/efeumutaslan/SAP-SKILLSWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-testing-quality)<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-testing-quality"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-testing-quality/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-testing-quality"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-testing-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00085 | $0.03245 |
| Opus 5 | $0.00043 | $0.01622 |
| Sonnet 5 | $0.00017 | $0.00649 |
| Haiku 4.5 | $0.00009 | $0.00325 |
Grade A, and why
sap-testing-quality scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Testing & Quality Assurance
Related Skills
sap-rap-comprehensive— RAP BO testing patterns, EML-based test assertionssap-devops-cicd— Integrating tests into CI/CD pipelines, ATC in CIsap-fiori-testing— wdi5/OPA5 E2E tests for Fiori/UI5 appssap-abap-advanced— ABAP Cloud test patterns with released API constraintssap-cloud-alm— Cloud ALM Test Management for enterprise test orchestration
Quick Start
Choose your testing approach:
| Layer | Framework | Tool |
|---|---|---|
| ABAP backend logic | ABAP Unit | ADT Test Runner / ATC |
| ABAP SQL / CDS | CDS Test Double Framework | CL_CDS_TEST_ENVIRONMENT |
| RAP Business Objects | RAP BO Test | EML + CL_BOTD_TXBUFDBL_BO_TEST_ENV |
| CAP Node.js services | cds.test + Jest/Mocha | cds test CLI |
| CAP Java services | JUnit 5 + Spring Test | mvn test |
| UI5/Fiori frontend | OPA5 + QUnit | UI5 Test Runner |
| API contract testing | REST/OData assertions | Postman / Newman / custom |
| Performance | JMeter / k6 | Load test scripts |
Core Concepts
ABAP Unit Architecture
- Test classes: Local class with
FOR TESTINGaddition - Risk levels:
HARMLESS,DANGEROUS,CRITICAL— controls what DB changes are allowed - Duration:
SHORT(<1s),MEDIUM(<10s),LONG(>10s) - Test isolation: Use test doubles to isolate unit under test from DB, authority checks, etc.
- Test relations:
FOR TESTING RISK LEVELannotations on test class definition
Test Double Frameworks
| Framework | Class | Purpose |
|---|---|---|
| ABAP Test Double Framework | CL_ABAP_TESTDOUBLE |
Mock any interface |
| SQL Test Environment | CL_OSQL_TEST_ENVIRONMENT |
Redirect DB tables to test data |
| CDS Test Double | CL_CDS_TEST_ENVIRONMENT |
Test CDS views with mock data |
| Authority Check Double | CL_AUNIT_AUTHORITY_CHECK |
Stub authority checks |
| RAP BO Test Double | CL_BOTD_TXBUFDBL_BO_TEST_ENV |
Test RAP BOs without DB |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 336 lines · 85 tokens per session scan A 966f1540b9db
sap-testing-quality is a skill published in the GitHub repository efeumutaslan/SAP-SKILLS (5 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 3,245 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
build-scripts
Standalone Phase 6 of SAP UI testing. Rediscovers the configured test folder, program, approved cases, and primary system from disk; validates upstream inputs; then writes one tests/ /test-scripts/TC-XXX.spec.ts per case using @sap-testing/runtime. Use when the user asks to write, generate, or convert Playwright…
design-cases
Standalone Phase 3 of SAP UI testing. Turns the findings.md decision surface and the screens.md control map into one tests/ /test-cases/TC-XXX.md per candidate case — grounded in the actual code behaviour (overlap/dedup/boundary), with a per-case selection-screen state table and a mandatory post-test verification…
explore-ui
Standalone Phase 2 of SAP UI testing. Opens the target transaction in a real browser (SAP WebGUI) and explores it live to produce tests/ /test-cases/screens.md — the authoritative map of every on-screen control, its accessible name/label as Playwright will see it, and its initial state. This is about how the UI…
run-scripts
Standalone Phase 7 of SAP UI testing. Rediscovers the configured test folder, program/specs, test cases, prepared data, and target system from disk; then runs Playwright via SAP Testing tools, generates .docx evidence, and diagnoses test script failures. Use when the user asks to execute tests, run TC-XXX, generate…
sap-testing
Entry point for the SAP UI test-automation environment. Explains project layout, the configured test folder, available tools, phase workflows, and bounded agent delegation. Use when the user asks about SAP UI testing, Playwright for SAP, writing tests for any ABAP report/transaction/process, generating test evidence…
helpers-reference
Reference for the bundled SAP Testing runtime (SapSession, SapArtifacts, resolveTestData, buildFixture, format helpers), importable in specs as "@sap-testing/runtime". Use when the user asks how a helper works or why a capability seems missing. Load sap-webgui for rendering, locator, theme, iframe, and…