Security Auth
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.
Clean ABAP StyleGuides. Apply Clean ABAP guidance when creating, refactoring, reviewing, or explaining ABAP artifacts such as classes, interfaces, reports, function modules, and unit tests.
Use when building business objects with the ABAP RESTful Application Programming Model (RAP): CDS view entity, behavior definition BDEF, behavior implementation ABAP class, managed RAP, unmanaged RAP, validation, determination, action, draft-enabled, service definition, service binding, OData V4, projection view, business object BO, S/4HANA BTP ABAP environment cloud development.
Use when deploying a SAP CAP application to SAP BTP: MTA descriptor (mta.yaml), Cloud Foundry manifest, Kyma / Kubernetes deployment, HANA Cloud provisioning, HDI containers, service bindings, environment variables, or build/deploy pipelines.