ratl.ai
Try Now ↗
  • Welcome
  • Getting Started
    • Quickstart
    • Understanding Testing Modes
  • MANAGE ACCOUNT
    • Organizations and Workspaces
    • Managing API Keys
  • FEATURES
    • Overview
    • Understanding Dashboard: A Complete Guide
    • Talking to Agents: A Comprehensive Guide for Interactions
    • API Functional Tests: A Comprehensive Solution for Automated Testing
    • Load and Performance Testing: A Comprehensive Solution for High Traffic Simulation
    • API Integration E2E Tests: A Comprehensive Solution for Automated Integration Testing
    • Web Automation: AI-Powered Visual Testing Solution
    • Schedules: Automate and Manage Test Execution Timing
    • Run History: Tracking and Managing Your Test Executions
  • INTEGRATIONS
    • Overview
    • CI/CD Integration: Automate Testing in Your Development Pipelines
    • Slack Integration: Real-Time Test Updates and Collaboration
    • Azure DevOps (ADO) Integration: Streamline Bug Tracking
    • Jira Integration: Simplify Bug Tracking and Test Management
    • Kubernetes Integration: Deploy Ratl Load Injectors On-Premises
  • CREDITS
    • Credit Management Overview
  • PUBLIC APIs
    • API Documentation
Powered by GitBook
On this page
  • Key Benefits
  • How to Use the Run History Feature
  • Postconditions
  • Expanding Run History Across Features
  • Conclusion
  1. FEATURES

Run History: Tracking and Managing Your Test Executions

PreviousSchedules: Automate and Manage Test Execution TimingNextOverview

Last updated 4 months ago

The Run History feature in Ratl enables users to track and analyze the execution history of their tests across Functional Tests, Integration Tests, Load Tests, and Accessibility Tests. This feature provides a detailed log of past executions, making it easier to identify and address issues.


Key Benefits

  • Comprehensive Execution Logs: Provides a complete history of test executions for easy reference.

  • Version Tracking: Allows users to track the test execution history for specific versions.

  • Quick Re-execution: Enables re-execution of specific tests directly from the run history.

  • Issue Resolution Insights: Helps identify when and where issues occurred and when they were resolved.


How to Use the Run History Feature

Step 1: Navigate to the Run History

  • Navigate to the desired test type (e.g., Functional Tests).

  • Select the specific test suite and click on Run History from the Actions Menu.

Step 2: Review Execution History

  • View the list of all past executions for the selected test suite.

  • Users can access details such as:

    1. Test Case Name: Name of the test case executed.

    2. Triggered On: Date and time when the test was triggered.

    3. Triggered By: Method of triggering (e.g., scheduled, manual).

    4. Status: Status of the test execution (e.g., Passed, Failed).

Step 3: Re-execute Tests

  • Select a specific execution from the history.

  • Click on Run to re-execute the selected test case.

  • Monitor the status of the re-executed test to verify if issues have been resolved.


Postconditions

  • Users can analyze the complete execution history of their tests.

  • Any failed tests can be re-executed to validate fixes.

  • Provides insights into version-specific issues, helping teams identify patterns and trends.


Expanding Run History Across Features

The Run History feature works seamlessly across all test types:

  1. Functional Tests: Track execution history for functional validations.

  2. Integration Tests: Monitor execution trends and resolve integration-specific issues.

  3. Load Tests: Access historical performance metrics to ensure system reliability.

  4. Accessibility Tests: Verify accessibility compliance across versions and re-run failed tests.

Each feature follows the same process as described above, ensuring a consistent user experience.


Conclusion

The Run History feature in Ratl empowers teams to efficiently manage and analyze test executions. By offering detailed insights into execution history, it helps streamline testing workflows and accelerates issue resolution.