Create Your First Project

Overview

Creating your first project is the foundation for organizing your testing efforts in ConductorQA. A project represents a collection of test suites and cases for one or more related applications.

Before You Start

Make sure you have:

• ✅ Completed your account setup
• ✅ Understand the core concepts
• ✅ Access to the ConductorQA platform

Step 1: Access Project Creation

Navigate to Projects

1. Log in to your ConductorQA account
2. From the main dashboard, click “Projects” in the sidebar
3. Click the “Create New Project” button

Project Creation Form

The project creation form includes several important fields that define your project structure.

Step 2: Configure Basic Information

Project Name

• Requirement: Must be unique within your organization
• Best Practice: Use descriptive names like “E-commerce Platform”, “Mobile App”, or “API Gateway”
• Example: "Customer Portal Testing"

Project Description

• Purpose: Explain what this project covers
• Best Practice: Include application scope, testing focus, and team information
• Example: "Comprehensive testing for customer-facing portal including UI, API, and integration tests"

Project Code (Optional)

• Purpose: Short identifier for easy reference
• Format: 2-6 characters, uppercase letters and numbers
• Example: "CUST" for Customer Portal, "API" for API testing

Step 3: Configure Application Settings

Multi-Application Support

ConductorQA supports testing multiple applications within a single project:

Single Application Project

• Use Case: Testing one specific application
• Setup: Leave applications field empty (defaults to single app)
• Example: Mobile app testing, specific microservice

Multi-Application Project

• Use Case: Testing related applications together
• Setup: Define multiple applications
• Example: Frontend + Backend + Database testing

Application Configuration

For each application in your project:

1. Application Name: Clear, descriptive name
2. Application Type: Frontend, Backend, API, Database, etc.
3. Environment URLs: Development, staging, production
4. Contact Person: Developer or owner contact

Step 4: Set Project Permissions

Team Access

Configure who can access your project:

Project Roles

• Owner: Full control including deletion
• Admin: Manage tests, users, but cannot delete project
• Editor: Create and modify tests and test runs
• Viewer: Read-only access to tests and results

Adding Team Members

1. Click “Add Team Member”
2. Enter email address or select from organization
3. Choose appropriate role
4. Click “Add”

Project Visibility

Choose project visibility level:

• Private: Only invited members can access
• Organization: All organization members can view
• Public: Visible to all (rarely used)

Step 5: Configure Testing Settings

Default Test Priorities

Set up priority levels for your test cases:

• Critical: Production-blocking issues
• High: Important functionality
• Medium: Standard features
• Low: Nice-to-have features

Automation Settings

Configure automation tracking:

• Automation Status: Track which tests are automated
• Integration Setup: Prepare for API integration
• CI/CD Planning: Consider continuous integration needs

Step 6: Review and Create

Pre-Creation Checklist

Before creating your project, verify:

• ✅ Project name is descriptive and unique
• ✅ Team members have appropriate access
• ✅ Application settings are configured
• ✅ Testing priorities align with your needs

Create the Project

1. Review all settings carefully
2. Click “Create Project”
3. Wait for confirmation message
4. You’ll be redirected to your new project dashboard

Step 7: Initial Project Setup

Project Dashboard Overview

Your new project dashboard shows:

• Project Statistics: Test counts, execution status
• Recent Activity: Latest test runs and updates
• Team Overview: Current team members and roles
• Quick Actions: Create test suites, run tests

Next Steps After Creation

1. Create Test Suites: Organize tests into logical groups
2. Add Test Cases: Create your first test cases
3. Set Up API Integration: Configure external test reporting
4. Invite Team Members: Add additional team members if needed

Project Management Best Practices

Naming Conventions

Project Names

• Use clear, descriptive names
• Include application or system name
• Avoid abbreviations unless universally understood
• Examples: “E-commerce Web Platform”, “Mobile Banking App”

Application Names

• Distinguish between different components
• Examples: “Web Frontend”, “REST API”, “Background Jobs”

Organization Strategy

By Application Architecture

Project: "E-commerce Platform"
├── Web Frontend
├── REST API
├── Payment Service
└── Admin Dashboard

By Testing Phase

Project: "Mobile App Release 2.1"
├── Unit Tests
├── Integration Tests
├── E2E Tests
└── Performance Tests

Team Structure

Small Teams (1-3 people)

• Everyone as Editor or Admin
• Simple permission structure
• Focus on testing over access control

Medium Teams (4-10 people)

• Clear Owner designation
• Mix of Admins and Editors
• Viewers for stakeholders

Large Teams (10+ people)

• Multiple Admins for different areas
• Role-based access by component
• Regular permission reviews

Common Setup Scenarios

Scenario 1: Single Web Application

Project Setup:

• Name: “Company Website Testing”
• Applications: Web Frontend only
• Team: 2-3 QA engineers as Editors
• Priority: Critical/High focus on core user flows

Scenario 2: Microservices Architecture

Project Setup:

• Name: “Order Management System”
• Applications: Order API, Payment API, Notification Service
• Team: Multiple teams with component-specific access
• Priority: Integration testing focus

Scenario 3: Mobile + Backend

Project Setup:

• Name: “Mobile Banking Application”
• Applications: iOS App, Android App, Backend API
• Team: Mobile QA team and API testing team
• Priority: Cross-platform consistency testing

Troubleshooting

Common Issues

Cannot Create Project

• Check organization limits
• Verify project name uniqueness
• Ensure proper permissions

Team Members Cannot Access

• Verify email addresses
• Check role assignments
• Confirm organization membership

Applications Not Showing

• Refresh browser
• Check application configuration
• Verify project settings

Getting Help

If you encounter issues:

1. Check project settings and permissions
2. Review organization settings
3. Contact your platform administrator
4. Refer to the troubleshooting guide

Next Steps

Now that you’ve created your first project:

1. Create Your First Test Suite - Organize your tests
2. Follow the Quick Start Guide - Complete end-to-end setup
3. Explore Project Management - Advanced project features
4. Set Up Team Collaboration - Work effectively with your team

Ready to organize your tests? Continue with creating your first test suite to start structuring your testing approach.