Organizes your testing infrastructure with Applications and Environments
QA.tech uses a hierarchical structure of applications and environments to organize your testing infrastructure and provide context-aware test execution.A single project may have one or more applications.
An application represents a single app that you want to test. It serves as a container for relevant test cases and environments. Each application has at least one environment, which contains properties (e.g., the URL) used by test cases within the application.
Environments represent different configurations of your application where tests can be executed. A single environment may contain various properties (like the website URL to test) which will be used by the agent when executing a test case. For example, you may have different environments for different language versions of your app.
Project├── Frontend│ ├── Environment A (Development)│ ├── Environment B (Staging)│ └── Environment C (Production)├── Admin app│ ├── Environment D (Test)│ └── Environment E (Production)└── API └── Environment F (Development)
When creating a new test, you must assign it to an existing application. Executing a single test will use that application’s default environment by default, unless specified otherwise in the session overrides.You can run tests in different environment configurations by adding them to a test plan and selecting target environments in the test plan settings.
Clean up preview environments after feature completion
This hierarchical structure helps you organize your testing infrastructure efficiently while maintaining clear separation between different applications and their configurations.