2026-05-27 –, Work Lab II
Integrating the OIDF conformance suite into GitHub CI sounded easy—until it wasn’t. This talk shares real-world failures, CI-specific pitfalls, and hard-won lessons on turning flaky red tests into meaningful conformance signals.
The OIDF conformance suite is an essential tool for validating OAuth and OpenID Connect implementations. Running it manually is one thing; making it reliable and automated in GitHub CI is another story entirely. Because the main goal of every developer is to deploy to prod on a Friday evening right before the weekend!
This talk is a hands-on experience report covering:
- How to integrate the OIDF conformance suite into a GitHub CI pipeline for testing OID4VCI and OID4VP tests.
- Common pitfalls when running conformance tests in non-interactive, ephemeral environments
- CI-specific failure modes (timing, networking, state, configuration drift)
- Debugging strategies when the test output feels more like a riddle than a report
- What I would do differently if I had to set it up again (spoiler: several things)
Along the way, I’ll share concrete examples of errors I encountered, why they happened, and how I eventually got from “red CI, mild panic” to a stable and trustworthy setup.
The goal is not just to complain (although there will be some therapy), but to help others avoid the same traps.
Kudos already to Joseph who supported to my questions all the time!
