Create Your First Test Suite

Overview

Test suites are logical collections of related test cases that help organize your testing efforts. Creating your first test suite is essential for maintaining a structured approach to test management.

Before You Start

Ensure you have:

• ✅ Created your first project
• ✅ Understood platform concepts
• ✅ Access to your project dashboard

Step 1: Access Test Suite Creation

Navigate to Your Project

1. Log in to your ConductorQA account
2. Select your project from the projects list
3. Click on “Test Suites” in the project sidebar
4. Click the “Create New Test Suite” button

Test Suite Creation Interface

The test suite creation form allows you to define the structure and scope of your test collection.

Step 2: Configure Basic Information

Test Suite Name

• Requirement: Descriptive and unique within the project
• Best Practice: Reflect the functionality or feature being tested
• Examples:
  • "User Authentication Flow"
  • "Shopping Cart Functionality"
  • "API Data Validation"

Test Suite Description

• Purpose: Explain the scope and objectives
• Best Practice: Include testing goals, coverage areas, and success criteria
• Example: "Comprehensive testing of user login, registration, password reset, and session management features"

Test Suite Code (Optional)

• Purpose: Short identifier for quick reference
• Format: 3-8 characters, typically uppercase
• Example: "AUTH" for authentication, "CART" for shopping cart

Step 3: Configure Suite Settings

Application Assignment

If your project has multiple applications:

1. Select Target Application: Choose which application this suite tests
2. Cross-Application Testing: Select multiple apps if tests span applications
3. Application Priority: Set primary application for mixed suites

Testing Categories

Choose the primary testing category:

• Functional Testing: Core feature validation
• Integration Testing: System component interaction
• UI/UX Testing: User interface and experience
• API Testing: Backend service validation
• Performance Testing: Speed and load validation
• Security Testing: Vulnerability and access control
• Regression Testing: Existing functionality verification

Priority Level

Set the overall suite priority:

• Critical: Core business functionality, production blockers
• High: Important features, significant user impact
• Medium: Standard functionality, moderate impact
• Low: Nice-to-have features, minimal impact

Step 4: Plan Test Case Organization

Test Case Structure Planning

Before creating test cases, plan your organization:

Functional Grouping

Authentication Suite
├── Login Tests
│   ├── Valid Login
│   ├── Invalid Credentials
│   └── Account Lockout
├── Registration Tests
│   ├── New User Registration
│   ├── Duplicate Email Handling
│   └── Email Verification
└── Password Management
    ├── Password Reset
    ├── Password Change
    └── Password Strength Validation

User Journey Approach

E-commerce User Journey
├── Browse Products
├── Add to Cart
├── Checkout Process
├── Payment Processing
└── Order Confirmation

Test Case Naming Convention

Establish consistent naming:

• Format: [Component] - [Action] - [Expected Outcome]
• Examples:
  • "Login - Valid Credentials - Successful Authentication"
  • "Cart - Add Product - Item Count Updates"
  • "API - Invalid Request - Returns 400 Error"

Step 5: Create Initial Test Cases

Adding Your First Test Case

1. In your new test suite, click “Add Test Case”
2. Fill in the test case details:

Test Case Information

• Name: Descriptive test case title
• Description: What the test validates
• Priority: Critical, High, Medium, or Low
• Automation Status: Manual, Automated, or To Be Automated

Test Steps

Create detailed test steps:

Step Format:

1. Action: What to do
2. Expected Result: What should happen
3. Test Data: Required data or inputs

Example Test Steps:

Step 1: Navigate to login page
Expected: Login form is displayed with username and password fields

Step 2: Enter valid username "test@example.com"
Expected: Username field accepts input without errors

Step 3: Enter valid password "SecurePass123"
Expected: Password field shows masked characters

Step 4: Click "Login" button
Expected: User is redirected to dashboard with welcome message

Test Case Best Practices

Clear and Specific Steps

• Use action-oriented language
• Include specific test data
• Define clear expected results
• Make steps reproducible

Proper Test Data

• Use realistic but safe test data
• Avoid production data in test cases
• Document any special data requirements
• Consider data cleanup needs

Maintainable Structure

• Keep test cases focused and atomic
• Avoid overly complex multi-step scenarios
• Use preconditions to set up test state
• Document any dependencies

Step 6: Configure Suite Execution Settings

Execution Order

Define how tests should be executed:

• Sequential: Tests run in defined order
• Parallel: Tests can run independently
• Grouped: Related tests run together

Prerequisites and Setup

Document any required setup:

• Environment Requirements: Specific configurations needed
• Test Data Setup: Required data or user accounts
• System State: Initial system conditions
• Dependencies: Other tests or suites that must run first

Post-Execution Actions

Define cleanup requirements:

• Data Cleanup: Remove test data after execution
• State Reset: Return system to initial state
• Log Collection: Gather relevant logs and artifacts

Step 7: Review and Activate Suite

Pre-Activation Checklist

Before activating your test suite:

• ✅ All test cases have clear, actionable steps
• ✅ Expected results are specific and measurable
• ✅ Test data requirements are documented
• ✅ Prerequisites and setup steps are defined
• ✅ Team members have appropriate access

Activate Your Test Suite

1. Review all test cases for completeness
2. Verify test execution settings
3. Click “Activate Test Suite”
4. Your suite is now ready for test execution

Test Suite Organization Strategies

By Feature Area

Advantages:

• Easy to find related tests
• Clear ownership boundaries
• Matches development structure

Example Structure:

E-commerce Platform
├── User Management Suite
├── Product Catalog Suite
├── Shopping Cart Suite
├── Checkout Process Suite
└── Order Management Suite

By Test Type

Advantages:

• Clear testing methodology
• Easy to schedule different test types
• Supports specialized testing teams

Example Structure:

Mobile Banking App
├── Smoke Test Suite
├── Functional Test Suite
├── Integration Test Suite
├── Security Test Suite
└── Performance Test Suite

By User Role

Advantages:

• User-centric testing approach
• Easy stakeholder communication
• Natural test scenario flow

Example Structure:

Project Management Tool
├── Admin User Suite
├── Project Manager Suite
├── Team Member Suite
└── Guest User Suite

Advanced Suite Configuration

Tags and Labels

Use tags for advanced organization:

• Environment Tags: @staging, @production
• Feature Tags: @authentication, @payment
• Priority Tags: @critical, @regression
• Team Tags: @frontend, @backend, @api

Custom Fields

Add custom fields for specific tracking needs:

• Business Value: Track feature importance
• Risk Level: Identify high-risk areas
• Automation Readiness: Plan automation efforts
• Customer Impact: Assess user-facing changes

Common Scenarios

Scenario 1: Web Application Testing

Suite Structure:

Web Application Suite
├── User Interface Tests
├── Form Validation Tests
├── Navigation Tests
├── Browser Compatibility Tests
└── Responsive Design Tests

Scenario 2: API Testing

Suite Structure:

REST API Suite
├── Authentication Endpoints
├── CRUD Operations
├── Data Validation
├── Error Handling
└── Performance Tests

Scenario 3: Mobile App Testing

Suite Structure:

Mobile App Suite
├── Core Functionality
├── Device Compatibility
├── Network Conditions
├── App Store Compliance
└── Security Features

Troubleshooting

Common Issues

Cannot Create Test Cases

• Check suite permissions
• Verify project access
• Ensure suite is properly configured

Test Steps Not Saving

• Check required field completion
• Verify step format
• Try refreshing the browser

Suite Not Appearing in Project

• Confirm suite creation completion
• Check project selection
• Verify user permissions

Getting Help

If you encounter issues:

1. Review suite configuration settings
2. Check project permissions and access
3. Contact your team lead or administrator
4. Refer to the troubleshooting guide

Next Steps

Now that you’ve created your first test suite:

1. Complete the Quick Start Guide - Run your first test
2. Explore Test Execution - Learn to run and monitor tests
3. Learn Test Suite Organization - Advanced suite management
4. Set Up Team Collaboration - Work with your team effectively

Ready to run your tests? Continue with the Quick Start Guide to execute your first test run and see results in action.