This section outlines the standard workflow used by CI/CD systems to authenticate, trigger Drizz test executions, and evaluate results as part of automated build and release pipelines.
End-to-End Pipeline Flow:
CI/CD pipeline requests an Auth0 access token
Optional: Uploads a new APK build artifact
Triggers one or more Drizz test plans
Parses execution response for status and execution IDs
Fails or passes the pipeline based on test execution outcome
