Release note·

    Switch Between Environments Effortlessly

    Manually updating URLs and configurations when switching between staging and production environments slows down testing workflows—so we added support for multiple environments per application. How It Works Per-Applicatio

    Manually updating URLs and configurations when switching between staging and production environments slows down testing workflows—so we added support for multiple environments per application.

    How It Works

    • Per-Application Environments: Define multiple environments (staging, production, development) for each application in your project, with unique URLs and configurations specific to each environment.
    • One-Click Switching: Switch between environments instantly when running tests, eliminating manual URL changes and configuration updates that previously required editing test cases.
    • Environment-Specific Configs: Set environment-specific authentication credentials, base URLs, and settings that automatically apply when tests run against that environment.

    Configure environments in your project settings under Applications, where you can add staging, production, and custom environments with their own URLs and configurations for seamless testing across your deployment pipeline.

    Ready to end the QA bottleneck?

    See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.

    Get a demo