Project Operations

Overview

Project creation establishes the foundation for your test suite: scope, environments, execution defaults, and who can change what.

Create a project (initial setup)

When creating a new project:

1. Define identity:
   • unique name
   • clear description
   • owner/team alignment
2. Choose defaults:
   • initial environment (start with dev/stage)
   • project visibility (private/team/org as applicable)

Set project scope

Define the boundaries and characteristics of your project:

• What’s in scope: services, versions, and the API surface you expect to cover.
• What’s out of scope: endpoints you intentionally exclude, and why.
• Technical parameters: base URL(s), auth method, and any rate limiting constraints.

Related: Configuration fundamentals.

Configure project-level defaults

Establish global settings that apply to all tests within the project:

• Execution: timeouts, retries for transient failures, and parallel limits.
• Data: seeding strategy and how you avoid cross-run collisions.
• Notifications: who gets alerted and where.

Assign team access

Control who can access and modify the project:

• Assign roles that match responsibility (Admin, Tester/Editor, Viewer).
• Use least privilege by default; expand permissions only when needed.

Related: Role permissions and Audit logs.

Related articles

• Project settings
• Managing projects