Skip to main content
QA.tech uses a hierarchical structure of projects, applications, and environments to organize your testing infrastructure. Understanding when to use each level helps you maximize test reuse and build efficient CI/CD workflows.

​
Understanding the Hierarchy

​
Organizations

Organizations are the top-level container for your company or team. They contain multiple projects and manage billing and team access at the organization level.

​
Projects

Projects are containers for team access and complete isolation between product lines. Use separate projects only when there are no possible shared user flows between the things being tested. For example:
  • Completely separate product lines with no shared functionality
  • Different teams that need complete isolation
  • A consultant working with completely separate clients

​
Applications & Environments

Applications represent distinct apps or services with their own test suites. Environments represent different deployments of the same application (e.g., staging, production, PR previews). See Applications & Environments for a full explanation of when to use each.

​
Example: Full Hierarchy

Organization: Pet Solutions Ltd
Why separate projects: Veterinary App and Netflix for Pets have no shared user flows — they’re completely separate products. Different products within the same team should typically be different Applications, not Projects. Only create separate Projects when there’s no possible shared user flows (like a consultant working with isolated clients).

​
Decision Guide

If you’re unsure which level to use, use this decision flowchart:
Golden rule: Create a new project only when there are no possible shared user flows. Different products within the same team should be different Applications, not Projects.