Trigger multiple packs

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.

Run the same flows with multiple configurations

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.

• Select specific Flows or Flow tags

• Apply value overrides

• Provide multiple value sets

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

• Expand coverage without editing pipelines

• Test multiple configurations from a single deployment event

• Keep CI logic simple while increasing validation depth

• Any provided value overwrites the stored value

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

• Safe defaults remain intact

• Only intended changes are applied

• You avoid redefining full configurations for every pack

Two ways to trigger multiple packs

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.

Hierarchical value merging

Test multiple configurations from a single deployment event

Keep CI logic simple while increasing validation depth

Real-world use cases

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

Any value not provided continues to inherit from the Value Store

Feature flags and code versions

You avoid redefining full configurations for every pack

Each language executes independently with isolated results.

Built for complex applications

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

Trigger packs for different application states such as:

More coverage without more duplication

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.

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 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.