Testing in your CD Pipelines – the CDEvents way
summary
CDEvents adds a small testing model that claims to let any test tool plug into event-driven CI/CD by emitting three subjects (test case run, test suite run, test output published) with predicates like queued/started/finished. Schemas require only ID, environment and outcome for runs and require format+source for outputs. Demo uses Testkube + curl and webhook.site, showing started/finished events delivered but no output event yet. Queued and outputs remain optional, so behavior depends on each implementation.
AI-written summary · about
chapters (10)
- 0:00CDEvents and testing pipelines
- 1:03What are CDEvents and why they matter
- 3:55Testing events in CDEvents
- 4:38Test case and suite run events
- 8:51Test output events importance
- 12:27Trigger objects in testing
- 13:32Required fields and sequences
- 15:39Testing events use cases
- 17:45Live demo in TestCube
- 19:52Call to action
related talks
19mAdopting CDEvents and Embracing Interoperability
06mEvents in CI/CD
08mBuilding a Future of Greater Interoperability in CI/CD with CDEvents
36mBuilding DevOps Metrics for your Choice of CD Tools Through CDE...
30mCI/CD Observability: Standardizing with CDEvents
22mCDEvents as Catalyst to Innovation in CI/CD Ecosystem
17mLet's Work Together! : CI/CD Interoperability using CDEvents
06mCDEvents Roadmap