Test Run Configuration

Test Run Configuration Test Runs in QA Sphere are a crucial part of the software development lifecycle, helping ensure that products meet quality standards before release. They involve executing predefined test cases to evaluate the functionality, performance, and reliability of a software application or system.

Creating a New Test Run

There are two ways to create a new test run:

Method 1: Using the Test Runs Tab

1. Navigate to the Test Runs tab.
2. Click on the Create Test Run button.

Method 2: From the Test Cases Tab

1. In the Test Cases tab, select a folder containing the desired test cases.
2. Click the options icon next to the folder name.
3. Choose Create Test Run with Folder. This will automatically include all test cases from the selected folder in your new test run.

Configuring Your Test Run

The key steps in configuring your test run are:

1. Assign a title and description to clearly identify the purpose of the test run.
2. Designate a responsible executive to oversee the test run.
3. Select or create a new milestone to associate with this test run.
4. Choose your preferred flexibility option based on your project needs.
5. Add folders containing the test cases you want to include in this run.

Understanding Key Concepts

What are Milestones?

Milestones in QA Sphere are significant points or stages in your project's timeline. They help you:

• Organize and group related test runs
• Track progress towards specific project goals or releases
• Manage deadlines and prioritize testing efforts

For example, you might create milestones like "Version 1.0 Release", "Q4 Security Audit", or "New Feature Beta Testing". By associating test runs with milestones, you can easily monitor testing progress for each important phase of your project.

Test Run Flexibility Options

When creating a test run, you can choose how it handles updates to test cases. Understanding these options is crucial for effective test management:

1. Live:

   • The test run automatically updates to reflect any changes made to included test cases.
   • Best for: Ongoing projects where test cases are frequently updated and you always want the latest versions.

2. Fixed Structure:

   • Preserves the current folder composition of selected test cases, ignoring structural changes.
   • Best for: When you want to maintain the organization of your test cases at the time of creating the test run, even if the folder structure changes later.

3. Fixed Version:

   • Maintains the current content version of test cases, ignoring any future updates.
   • Best for: When you need to ensure that the test run uses a specific version of test cases, such as for compliance audits or when testing a particular software version.

Choosing the right option depends on your project's needs:

• If you're working on a rapidly evolving product, Live might be best to ensure you're always testing the most up-to-date scenarios.
• For a major release where you want to lock in a specific set of tests, Fixed Version could be more appropriate.
• Fixed Structure is useful when you want to preserve the organization of your tests but allow for content updates.

Adding Test Cases

To include specific test cases in your test run:

1. Click Add Folder in the Create Test Run form.
2. Select the folders with the test cases you want to include.

When setting up your test run, consider the following:

• Scope: Carefully select which test cases to include based on the goals of this particular test run.
• Responsibility: Assign the test run to the team member best suited to oversee its execution.
• Timing: Choose the appropriate milestone to ensure the test run aligns with your project timeline.
• Flexibility: Select the option that best fits how you want to handle test case updates for this run.

By thoughtfully configuring your test runs, you can streamline your quality assurance process, improve collaboration among team members, and enhance the overall reliability of your software products.