Test Organization

This guide explains how to organize your tests effectively using TrueAssert's project and organization structure.

Overview

TrueAssert uses a hierarchical structure for organizing tests:

  • Organizations: Top-level grouping (companies, teams)

  • Projects: Sub-grouping within organizations (applications, features)

  • Tests: Individual test cases within projects

Organization Structure

Organizations

Organizations are the top-level grouping:

  • Each user can belong to multiple organizations

  • Organizations have members with different roles

  • Tests belong to projects, which belong to organizations

Use Cases:

  • Separate companies or clients

  • Different teams or departments

  • Different environments (staging, production)

Projects

Projects group related tests:

  • Each project belongs to one organization

  • Projects have their own settings (login, session)

  • Tests are created within projects

Use Cases:

  • Different applications

  • Different features or modules

  • Different test suites

Tests

Tests are individual test cases:

  • Each test belongs to one project

  • Tests can be organized by functionality

  • Tests have versions for tracking changes

Creating Structure

Default Setup

When you create an account:

  1. Default organization is created automatically

  2. Default project is created in that organization

  3. You're added as a member

Creating New Projects

  1. Navigate to project settings or test list

  2. Create new project (if interface available)

  3. Or use first project for all tests

Note: Currently, TrueAssert uses the first project in your organization for test creation. You can create additional projects if needed.

Best Practices

Organization Strategy

  1. By Company/Client: One organization per company

  2. By Team: One organization per team

  3. By Environment: Separate organizations for staging/production

Project Strategy

  1. By Application: One project per application

  2. By Feature: One project per major feature

  3. By Test Suite: One project per test suite type

Test Naming

  1. Descriptive Names: Clear, descriptive test names

  2. Consistent Format: Use consistent naming convention

  3. Include Context: Include what the test covers

Examples:

  • Login Flow - Valid Credentials

  • Checkout Process - Credit Card

  • User Registration - Email Validation

Project Settings

Login Settings

Configure authentication per project:

  • Login URL: Where users log in

  • Login Username: Username for authentication

  • Login Password: Password for authentication

Access: /project/{project_id}/settings/login/

Session Settings

Manage browser sessions per project:

  • View saved sessions

  • Clear sessions

  • Import sessions from PowerShell/cURL

Access: /project/{project_id}/settings/session/

Test Management

Test Status

Tests have different statuses:

  • DRAFTING: Being generated or edited

  • REVIEW: Ready for review

  • READY: Ready to execute

  • ARCHIVED: No longer active

Test Versioning

Tests have versions:

  • Version increments when steps change

  • Executions track which version was used

  • Old executions show "version mismatch" if test changed

Test Organization Tips

  1. Group Related Tests: Keep related tests in same project

  2. Use Clear Names: Make test purposes obvious

  3. Archive Old Tests: Archive tests no longer needed

  4. Review Regularly: Review and update tests periodically

Permissions

Organization Membership

Users can belong to multiple organizations:

  • Owner: Full control

  • Member: Can create/edit tests

  • Viewer: Read-only access

Project Access

Access to projects is based on organization membership:

  • Members of organization can access all projects

  • Tests inherit project permissions

Related Topics

← Back to Documentation

PreviousAdvancedNextPerformance Optimization

Last updated