How os-autoinst/openqa works
openQA is the web frontend and management half of an automated system-testing framework; the separate os-autoinst engine executes tests in virtual machines. Its principal workflow is users or automation submitting and managing tests through the web/API, the scheduler assigning work to workers, and workers invoking the test engine while reporting results. README supports these broad roles and capabilities, but the supplied source excerpts contain no runtime modules, so detailed calls and data transfers are not asserted.
Main entry points: WebAPI Web frontend · Scheduler Test scheduler · Worker Worker · Jobs Job management
Components 14
Web management
- Web frontend
lib/OpenQA/WebAPI - High-level API
lib/OpenQA/WebAPI/Controller/API - Test scheduler
lib/OpenQA/Scheduler - Job management
lib/OpenQA/Jobs - Test results
lib/OpenQA/Parser/Result - Live updates
lib/OpenQA/WebSockets - Live test view
lib/OpenQA/LiveHandler - OBS integration
lib/OpenQA/WebAPI/Plugin/ObsRsync
Test execution
- Worker
lib/OpenQA/Worker - Test engine
Shared state and assets
- Persistent data
lib/OpenQA/Schema - Test assets
lib/OpenQA/Task/Asset - Cache service
lib/OpenQA/CacheService
Other components
- User or automation
Connections 12
- User or automation → Web frontend: uses
README.md - User or automation → High-level API: submits requests
README.md - Test scheduler → Job management: assigns work
- Worker → Test engine: runs tests
README.md - Worker → Test results: reports results
- Web frontend → Persistent data: manages records
- Test scheduler → Persistent data: reads job state
- Job management → Test assets: uses assets
- Web frontend → Live updates: publishes updates
- Live test view → Live updates: streams status
- Cache service → Test assets: caches assets
- OBS integration → High-level API: extends API