# Run group

Running groups enables you to execute multiple test suites together, maintaining organization and providing consolidated results. You can choose different environments and generate comprehensive reports for your test executions.

1. Navigate to the Groups page.
2. Find the group you want to run (e.g., "AirTable APIs").
3. Click the green "Run Group" button next to the group.

Before execution starts, you can configure:

1. Choose an environment from the dropdown (e.g., "DEFAULT").
2. Click "Select Environment" to confirm.
3. Options available:
   • Run all tests using the "Run all" button.
   • Generate a report using the "Generate Report" button.

• Run: Execute individual test suites.
• Details: View detailed test results.
• Go to test suite: Navigate to the test suite configuration.
• Generate Report: Create a comprehensive test report.

The interface shows:

• Number of tests executed (e.g., "3/3 tests executed").
• Tests passed (shown in green).
• Tests failed (shown in red).
• Tests without assertions.
• Running status indicator.

• Warning message: "Please do not close this page while the running of test suites is in progress."
• Real-time execution updates
• Test completion status

Each test suite in the group shows:

1. Test suite name.
2. Run button.
3. Details button.
4. Go to the test suite link.
5. Execution statistics:
   • Tests executed count
   • Passed tests count
   • Failed tests count
   • Tests without assertions

When you click the "Details" button for a test suite, you'll see a detailed breakdown of each test execution:

1. Test Description Column

   • Shows the purpose of each test.
   • Example test types:
     • "Test with missing compulsory fields to trigger error response."
     • "Test with an incorrect HTTP method."
     • "Test accessing an HTTPS endpoint with HTTP."

2. Status Code Column

   • Displays HTTP response codes
   • Common codes shown:
     • 200: Success
     • 401: Unauthorized
     • 404: Not Found

3. Result Column

   • Shows test outcome (e.g., "FAILED", "PASSED")
   • Color-coded for quick recognition:
     • Red for failed tests
     • Green for passed tests

The details view provides comprehensive statistics:

• Total tests executed (e.g., "3/3 tests executed")
• Number of passed tests (shown in green)
• Number of failed tests (shown in red)
• Tests without assertions (shown in yellow)
• Warning indicators (⚠️) when applicable

Test Suite: Json Generator Endpoint
- 15/16 tests executed
- 2 passed
- 2 failed
- 11 without assertions

Test Suite: Untitled test suite
- 4/4 tests executed
- 0 passed
- 4 failed
- 0 without assertions

• Play button (▶️) next to each test for individual test execution.
• Expandable test descriptions for more details.
• Quick access to full test suite via "Go to test suite" button.

1. Failed Tests

   • Review the status code to understand the type of failure.
   • Check the test description for expected behavior.
   • Common failure patterns:
     • Missing required fields
     • Incorrect HTTP methods
     • Protocol mismatches (HTTP vs HTTPS)

2. Tests Without Assertions

   • Indicates tests that ran but had no pass/fail criteria.
   • To add assertions, use the test suite page.
   • Marked with warning indicators when present.

3. Navigation and Control

   • Use "Run" to re-execute individual tests.
   • "Go to test suite" for test configuration.
   • "Details" to expand/collapse test information.

1. Analysis

   • Review failed tests first.
   • Check patterns in status codes.
   • Note tests without assertions for improvement.

2. Documentation

   • Use test descriptions for clear failure understanding.
   • Document unexpected status codes.
   • Track patterns across multiple runs.

3. Troubleshooting

   • Use status codes to identify issue types.
   • Compare similar test results.
   • Check for consistent failure patterns.

4. Reporting

   • Include a detailed view in test reports.
   • Highlight critical failures.
   • Track assertion coverage.

• Always verify the selected environment before running.
• Use consistent environments for related test suites.
• Document environment-specific configurations.

1. Wait for all tests to complete before navigating away.
2. Generate reports after execution for documentation.
3. Review failed tests immediately.
4. Check tests without assertions for completeness.
5. Use the details view for debugging failures.

• Run smaller groups first to verify the configuration.
• Use the "Run all" feature for comprehensive testing.
• Monitor execution progress for all test suites.
• Generate reports for documentation and analysis.
• Review execution results before proceeding with dependent tests.

1. Select the appropriate environment for your test run.
2. Choose between running individual test suites or the entire group.
3. Monitor the execution progress.
4. Review test results and generate reports.
5. Investigate and document any failures.
6. Export results for sharing or documentation.

Remember to wait for all test executions to complete before closing the page or navigating away from the results view.