> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qawolf.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose the right CI environment to execute your tests

> QA Wolf supports testing across any CI environment, so you can align testing goals with your existing release process.

Match your testing goals to the environment you run your tests in.

### Staging: When test stability matters most

Use your **Staging** (QA or Test) environment for the best balance between reliability and safety.

**What this gives you**

* Stable builds with predictable data.
* Space for complete end-to-end and regression testing.
* Safe configuration for allowlisted email domains or test credentials.

<Note>
  Staging may lag behind active development. If releases are infrequent, regressions might not surface until later in testing.
</Note>

### Development: Get rapid feedback during test development

Run tests in your **Development** environment to identify regressions early.

**What this gives you**

* Immediate feedback after merges.
* Quick iteration and faster bug turnaround.
* Tight integration with the development process.

<Note>
  Development environments can be unstable or inconsistent. Failing tests here often point to temporary issues rather than actual defects.
</Note>

### Production: Verify the real user experience

Run tests in **Production** when you need complete confidence in real-world behavior.

**What this gives you**

* Testing against the exact production configuration.
* Real performance and reliability data.
* Confirmation that core user flows work correctly in the live environment.

<Danger>
  Bugs discovered here have already reached users. Some flows (such as payments) may trigger real transactions or pose a financial risk.
</Danger>

### Preview environments: Validate changes before merging code

Ask QA Wolf to help you enable **PR testing** to run your flows automatically on each pull request in ephemeral preview environments.

**What this gives you**

* Early, automated feedback in your VCS.
* Confidence that merges won't break mainline tests.
* Faster, safer release cycles.

<Note>
  PR testing requires dedicated, isolated environments. Shared resources or reused credentials can cause flaky results.
</Note>

<Tip>
  QA Wolf recommends using [release candidates (RCs)](https://www.qawolf.com/blog/rcs-over-prs-how-rc-testing-aligns-velocity-and-quality) for PR testing.
</Tip>