Testing CAP and BTP Extensions
Course quiz
Testing CAP and BTP Extensions
Keep this: job aid
BTP extension test plan checklist
- Map each failure type to the cheapest level: service, UI, contract, integration, end-to-end.
- cds.test first in every test file; runner-agnostic tests; reset data per test.
- Test every rule and role positive and negative; never stub the CAP service itself.
- Mock remote services with realistic .csv data; keep failure mocks separate.
- Record a narrow contract per consumed API and event; check it in the pipeline and against CMQ after each support package.
- QUnit for UI logic, OPA5 for screens against mock data; browser end-to-end only for cross-app journeys.
- Run a readiness check before end-to-end; wait for conditions, never fixed times.
- Quality gates on every step; flaky tests are defects.
- Evidence package for the exact version going live, recorded in SAP Cloud ALM.