Run the same flows with multiple configurations

Trigger Multiple Packs is an execution capability within DoesQA that allows you to run the same Flows with multiple value sets in a single operation.

Instead of manually repeating runs for different environments, languages, currencies, or roles, you can provide an array of value sets and DoesQA will execute each configuration independently.

One trigger.

Multiple execution packs.

Full visibility.

Two ways to trigger multiple packs

1. Via Run Recipes

Recipes allow you to:

• Select specific Flows or Flow tags

• Apply value overrides

• Provide multiple value sets

• Trigger from the app, schedules, or CI/CD

If a Recipe contains an array of value sets, each entry becomes its own execution pack.

This is ideal for teams who want powerful control directly inside DoesQA without touching pipelines.

2. Via Webhook or CI/CD

When triggering DoesQA from CI/CD, you can provide an array of value sets in the webhook payload.

Each item in the array creates a separate run pack automatically.

This means you can:

• Expand coverage without editing pipelines

• Test multiple configurations from a single deployment event

• Keep CI logic simple while increasing validation depth

No duplication. No extra scripts.

Hierarchical value merging

When you provide value overrides, DoesQA performs a hierarchical merge with your Value Store.

• Any provided value overwrites the stored value

• Any value not provided continues to inherit from the Value Store

This ensures:

• Safe defaults remain intact

• Only intended changes are applied

• You avoid redefining full configurations for every pack

It is precise, controlled, and predictable.

Real-world use cases

Multi-environment testing

Run the same Flow against:

• Dev

• Staging

• Production

• Regional deployments

All in one structured operation.

Multi-language validation

Trigger packs for:

• English

• French

• German

• Spanish

Each language executes independently with isolated results.

Currency and pricing checks

Validate USD, GBP, EUR, or region-specific pricing without duplicating Flows.

Feature flags and code versions

Trigger packs for different application states such as:

• Feature flags enabled vs disabled

• A/B variants

• Beta vs stable releases

• Different API versions

• Versioned frontend builds

Instead of duplicating Flows for each flag or release variation, you can pass different value sets and validate how the same journeys behave under different configurations.

This is especially powerful when validating staged rollouts or testing new features safely before full release.

Data-driven testing at scale

Provide multiple datasets to validate:

• Subscription tiers

• Product variations

• Feature combinations

• API-driven configurations

Built for complex applications

As applications scale, single-run execution models become limiting.

Trigger Multiple Packs allows you to expand coverage without increasing Flow duplication or maintenance overhead.

It is designed for:

• Multi-region products

• Large teams

• Complex CI/CD strategies

• Feature-flag heavy systems

• Data-driven architectures

More coverage without more duplication

The goal is not simply more runs.

It is broader coverage you can trust, without increasing cognitive complexity.

Trigger Multiple Packs lets you validate multiple realities of your application in a structured, maintainable way.

One Flow.

Many scenarios.

Clear results.