Typical Integration Flow

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:

1. CI/CD pipeline requests an Auth0 access token

2. Optional: Uploads a new APK build artifact

3. Triggers one or more Drizz test plans

4. Parses execution response for status and execution IDs

5. Fails or passes the pipeline based on test execution outcome