Bootstrap off-stack ABAP Unit testing plus an abaplint static-analysis gate onto an abapGit-serialised ABAP repository, with no live SAP system. Use when you need to run a repo's existing ABAP Unit tests in CI (GitHub Actions) by transpiling serialised ABAP to JavaScript with the abaplint transpiler and open-abap-core and executing them on Node. Covers pinning the transpiler parse dialect to a specific SAP_BASIS release (e.g. v816), breaking a class-under-test free of heavy DDIC drag with a shim or factory seam, authoring minimal domain-less DDIC fixtures, a reproducible npm ci committed-lockfile setup, and wiring the off-stack unit-test job beside the abaplint lint job on every push and pull request. Triggers on "off-stack ABAP Unit", "transpiled ABAP Unit on Node", "abaplint transpiler CI", "run ABAP tests without a SAP system", "ABAP GitHub Actions unit tests", "abaplint new-repo bootstrap". Scope boundary is load-bearing: it verifies orchestration and pure-ABAP logic only; any class calling classic BAPIs, the database, or HTTP is shimmed and remains an on-stack ATC + ABAP Unit concern, and an off-stack green is CI-grade provenance, not an in-system verification.

Use when writing or reviewing tests for a SAP CAP application: unit tests, integration tests with cds.test, Vitest setup (recommended since CAP April 2026), jest setup, mocking services or databases, testing actions/functions, or test data management in SAP CAP Node.js projects.

Modernize QUnit unit tests and OPA5 integration tests to the UI5 Test Starter concept. Use this skill when: - The linter reports `prefer-test-starter` for *.qunit.html or *.qunit.js files - Test HTML files use manual sap-ui-core.js bootstrapping instead of Test Starter's runTest.js/createSuite.js - Test JS files use Core.ready(), Core.attachInit(), or jsUnitTestSuite instead of sap.ui.define - OPA test HTML files exist with per-test Opa5.extendConfig and manual bootstrapping - An AllJourneys.js orchestrator loads OPA journeys dynamically - OPA journeys call `iStartMyUIComponent` instead of `iStartMyAppInAFrame` - User asks to modernize tests, modernize test infrastructure, or adopt Test Starter Handles unit tests (Core.ready removal, sap.ui.define wrapping) and OPA challenges (page-object imports, Opa5 config, journey orchestration, QUnit 1.x assert modernization, in-window-to-iframe launcher migration). Trigger on: prefer-test-starter warnings, test modernization requests, iStartMyUIComponent.

This skill should be used in any OPA5 task - creating, modifying, extending, debugging, fixing or reviewing an integration test. Use when the user asks to "write an OPA5 test", "add an OPA5 journey", "fix the OPA5 test failure" or mentions OPA5 or its components - opaTest, page object, journey, waitFor.