Executing a Test Plan

Drizz provides a streamlined and reliable execution framework that allows teams to run Test Plans consistently across multiple environments. Execution can be triggered directly from the Drizz Dashboard or CI/CD, enabling both on-demand runs and scheduled or automated workflows. This ensures rapid validation, predictable regression coverage, and full observability into every run.

1. Executing via Drizz Dashboard

The Drizz Dashboard offers a manual, UI-driven execution experience which is ideal for quick validation, exploratory checks, and controlled test cycles.

Configurable options include:

1. Device Selection Choose between real devices, simulators, or emulators depending on your testing strategy.

2. OS Version & Platform Settings Run the same Test Plan across different OS versions to ensure compatibility and regression safety.

3. Parallel Execution Preferences Define how many tests should run concurrently to balance speed, resource usage, and stability.

4. Run Metadata & Naming Assign run names or labels for tracking, reporting, and audit purposes.

5. Environment Profiles Apply environment-specific app builds, network conditions, or backend configurations as needed.

Once triggered, Drizz automatically orchestrates the plan, handles concurrency, captures all artifacts, and provides real-time visibility into progress and results.

2. Executing a Test Plan via CI/CD

Drizz integrates seamlessly with modern CI/CD pipelines, enabling fully automated, repeatable, and scalable test execution as part of every build, deployment, or release cycle. This ensures that mobile quality checks are enforced continuously—without manual intervention.

How CI/CD Execution Works

Your pipeline (Jenkins, GitHub Actions, GitLab, Bitbucket, Azure DevOps, etc.) triggers a Drizz Test Plan run through Drizz’s secure APIs. The Test Plan executes on Drizz Cloud or your configured on-prem devices, and the results are pushed back to the pipeline for reporting and gating.

Key Capabilities:

1. Automated Regression on Every Build Trigger Test Plans during dev, staging, or production deployments to catch issues early.

2. Pipeline Gating & Quality Thresholds Fail builds automatically if test results don’t meet defined criteria (e.g., pass ≥ 90%, zero critical failures).

3. Environment-aware Execution Pass environment parameters (API base URLs, credentials, feature flags) directly from the pipeline.

4. Parallelized Execution at Scale Run large test suites concurrently across device farms for faster feedback cycles.

5. Unified Reporting CI/CD logs link back to the Drizz Dashboard for rich artifacts—screenshots, videos, step logs, and execution timelines.

For mode details on CI/CD check Documentation