원클릭으로
abap-test-loop
Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Differences and deterministic behavior of the mock ADT server used by adt-bench smoke runs.
How to return a strict scenario result JSON with evidence and no extra prose.
Standard ABAP object workflow (discover, create or edit, check, activate, validate).
| name | abap-test-loop |
| description | Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix. |
When the task is "make tests pass" or "produce a working implementation", iterate through this loop until the AUnit result is clean:
checkMessages body for errors./sap/bc/adt/abapunit/testruns; poll the run-status URI; fetch the JUnit-formatted result.Cap your iterations. If you have not produced a green result after a reasonable number of iterations (typically 3–5), report status: "partial" with a summary of what was tried and what still failed. Do not loop forever.