Menü
Differences and deterministic behavior of the mock ADT server used by adt-bench smoke runs.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
How to consume a GitHub issue body as an agent task prompt. The 9-section template, the lifecycle, the failure modes.
The 12 design principles this codebase is built on. Read first, before any task.
Spec-driven development — the practice of writing the spec before the code. With the 9-section template and the three pnpm spec-check gates.
How to return a strict scenario result JSON with evidence and no extra prose.
Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix.
Standard ABAP object workflow (discover, create or edit, check, activate, validate).
| name | abap-mock-usage |
| description | Differences and deterministic behavior of the mock ADT server used by adt-bench smoke runs. |
When the benchmark is running against the local mock ADT server (the default in v1), a few things differ from a real SAP system:
Basic (user demo, password demo). No X.509, no SNC, no OAuth.X-CSRF-Token: Fetch. POST/PUT currently do not enforce the token in v1.kind: "test" evidence only when the real backend is configured.__mock/* admin endpoints (/__mock/state, /__mock/reset, /__mock/stats) are not part of SAP ADT. Do not call them from production code; they exist only for the harness and the evaluator./__mock/stats returns { total, by_endpoint } counters that the harness uses for the optional metrics.adt_http_calls field.transportchecks is not implemented; the mock skips it and treats $TMP packages as local.When a scenario is run in mock mode, the prompt may include a "Mock ADT server" section with the URL. Use that URL as the base for your MCP server's ABAP_URL (or equivalent).