Test Run History

The Test Run History page in CheckView is a powerful tool for analyzing test performance, identifying patterns, and troubleshooting issues across your websites, plugins, and workflows.

Key Features of the Test Run History Page

  1. Comprehensive Test Data: View a detailed history of all test runs across your account and includes information on test statuses, websites, plugins, and test flow types.
  2. Filtering Options: Narrow down results to focus on specific tests, dates, or issues.
  3. Search Functionality: Quickly locate a specific test by entering its Test ID.

Using Filters for Targeted Analysis

The Test Run History page includes multiple filtering options to help you focus on relevant data:

  1. Date Filter
    • What It Does: Allows you to pinpoint test runs within a specific timeframe.
    • Use Case: Ideal for identifying patterns during a period when issues arose or changes were made to your site.
    • Pro Tip: Pair the date filter with status filtering to identify problem areas during a known outage or plugin update.
  2. Test Status Filter
    • What It Does: Filter tests by their outcome:
      • Passed: Tests that completed successfully.
      • Failed: Tests that encountered errors.
      • Pending: Tests that have not yet run or in-progress.
    • Use Case: Focus on failed tests to troubleshoot issues or analyze the stability of specific workflows.
    • Pro Tip: Use this filter alongside the Test Flow Type to identify recurring failures in specific workflows, such as checkout or form submissions.
  3. Website Filter
    • What It Does: Narrow results to test runs from a specific website.
    • Use Case: Helpful for accounts managing multiple websites to isolate performance or issue trends on individual sites.
    • Pro Tip: Combine the website filter with date and status filters to drill down into a specific site’s test history during a known period of instability.
  4. Test Flow Type or Plugin Filter
    • What It Does: Focus on tests related to a specific plugin or test flow type.
    • Use Case: Ideal for troubleshooting plugin-related issues, such as WooCommerce checkout or form plugin functionality.
    • Pro Tip: Use this filter after a plugin update to analyze its impact on test stability over time.
  5. Search by Test ID
    • What It Does: Directly locate a specific test using its unique Test ID.
    • Use Case: Useful for connecting multiple test failures over time or when collaborating with support teams.
    • Pro Tip: Keep a record of frequently failed Test IDs to track recurring issues or patterns.

Best Practices

  1. Identify Patterns: Regularly review test run history to detect recurring issues, such as failures related to specific plugins, workflows, or time periods.
  2. Combine Filters: Use multiple filters together (e.g., date, website, and test flow type) to narrow your focus and uncover deeper insights.
  3. Leverage Test IDs: Track Test IDs for failed tests to monitor ongoing issues or share details with your development team for faster resolution.
  4. Review After Updates: Use the page after deploying updates to plugins, themes, or core files to validate that changes haven’t introduced new issues.
  5. Monitor Success Rates: Track the ratio of passed vs. failed tests over time to gauge the overall health of your workflows.

The Test Run History page is an invaluable resource for maintaining the reliability and efficiency of your test flows. Regularly reviewing this page helps you stay ahead of potential problems and ensures optimal performance for your websites and plugins.un

Docs