Project Settings

Overview

Project settings define how test cases execute in each environment. Before running generated tests, verify base URLs, authentication, and test data sources so results are meaningful.

Core settings to configure first

Prioritize these settings when onboarding a new project:

• General project details: name and description
• Default environment: the primary target for manual test runs
• Base URL per environment: Dev, QA, Staging, or Production hosts
• Default headers: required headers shared across requests

Use Save changes after updates.

Authentication profiles

Set up authentication before executing tests:

• create a profile (API key, Bearer token, Basic auth, or equivalent)
• bind credentials at project or environment level
• validate the profile using endpoint tests

Test data and supporting assets

You can maintain supporting resources directly at project level:

• Test data files (CSV/JSON) for data-driven execution
• Requirement documents for traceability
• Data source connections used by test inputs or assertions

Change detection and maintenance

When API specs evolve, run change detection to identify:

• added endpoints
• modified request/response models
• removed operations that may affect existing tests

Review generated tests after major spec updates.

Access and lifecycle controls

• Assign team roles based on least privilege.
• Restrict settings changes to project owners/admins.
• Use delete actions only for obsolete projects after backup/export.

Lifecycle guidance: Managing projects.

Related configuration guides

• Configuration fundamentals
• Test configuration
• Role Permissions

Related articles

• Project
• Managing projects
• Project operations