# Run against production
export TEST_HOST=https://example.com
testpilot test login.pilot.yaml
```

## Parameterizing Other Test Values[​](#parameterizing-other-test-values "Direct link to Parameterizing Other Test Values")

You can parameterize any string value in your test files, not just URLs:

```yaml theme={null}
name: "User Registration Test"
context:
  - text: "Test registration with configurable user details"
cases:
  - id: "registration-001"
    name: "New User Registration"
    description: "Test new user registration process"
    url: "https://${TEST_HOST:-example.com}/register"
    steps:
      - "Fill in the registration form with email: ${TEST_EMAIL:[email protected]}"
      - "Set password to: ${TEST_PASSWORD:-SecurePass123!}"
      - "Complete registration and verify success"
```

## Use Cases for Parameterized Tests[​](#use-cases-for-parameterized-tests "Direct link to Use Cases for Parameterized Tests")

Parameterizing your tests is useful for:

1. **Environment Switching**: Run the same tests against dev, staging, and production
2. **Configuration Changes**: Test with different feature flags or settings
3. **Test Data Variation**: Use different test accounts or input data
4. **CI/CD Integration**: Configure tests differently based on the build environment
5. **Local Development**: Allow developers to point tests to their local instances

## Example in CI/CD Pipeline[​](#example-in-cicd-pipeline "Direct link to Example in CI/CD Pipeline")

Here's how you might use parameterized tests in a CI/CD pipeline:

```yaml theme={null}