ORDS Testing

An API without tests breaks with the first change. The workshop builds a test strategy for ORDS APIs that runs in the CI/CD pipeline and catches errors before consumers notice them.

Audience

Developers and testers responsible for ORDS APIs.

Modules

The modules are building blocks. You choose and weight them, and we agree on the agenda together beforehand.

• Test strategy: the test pyramid for database APIs, what gets tested where
• Unit tests: PL/SQL logic with utPLSQL, test data and isolation
• API tests: Postman collections, Newman, environments and variables
• Contract tests: checking against the OpenAPI specification
• Negative tests: error cases, boundary values, invalid input
• Load and security: load tests, auth tests, common vulnerabilities
• Pipeline: tests in GitLab CI or Azure DevOps, reports and quality gates

REST-Lib

Every ORDS workshop includes my REST-Lib: a PL/SQL library that standardizes recurring tasks such as response formats, error handling and parameter validation. It is handed over to your team together with the materials.

Outcome

A test suite for a real API from your environment and the pipeline that runs it on every change.

Preview

For a first look: the talks on this topic give you an overview, and the talk pages include the slides.

• Put your ORDS API to the Acid Test APEX Alpe Adria 2026