Organization and Structure Best Practices

1 min read

A clear structure helps teams find work quickly, assign ownership, and scale testing without confusion.

Workspace and Project Boundaries

Use a workspace for the team or organization boundary. Use projects for products, applications, services, or major testing areas.

Create a new project when:

Avoid creating projects for small variations that can be handled with folders, labels, test suites, or custom fields.

Use repository folders to organize test cases by feature, domain, or journey.

Good patterns include:

Keep folder depth shallow enough that testers can browse without getting lost.

Use test suites for execution intent, not long-term storage.

Common test suite patterns:

Test cases can be reused across suites, releases, executions, and test runs.

Use labels for lightweight categorization and filtering.

Use custom fields when the team needs structured metadata, required capture, or consistent dropdown values across supported work item types.

Do not add fields or labels unless the team will use them for filtering, reporting, ownership, or workflow decisions.

Use shared steps for repeated step groups and parameters for reusable non-secret values.

Review shared assets before editing or deleting them because changes can affect many test cases.