Maeris logo
Sign In

Test Run, Results & Test Information Modal

Learn how to execute your tests, interpret results, and access detailed test information in Maeris. This guide covers everything you need to know about running tests and analyzing outcomes.

Running Tests

There are several ways to execute tests in Maeris, depending on your needs and workflow.

Run Individual Test

Execute a single test case from the Notebook.

  1. Navigate to the Notebook
  2. Click on the test you want to run
  3. Click the "Run" button or use the play icon
  4. Monitor execution in real-time

Run Multiple Tests

Select and run multiple tests simultaneously.

  1. Select multiple tests using checkboxes
  2. Click "Run Selected" from the toolbar
  3. Tests will execute in parallel or sequentially based on configuration

Run Test Suite

Execute an entire test suite or regression pack.

Use the "Run Suite" option to execute all tests in a selected group or tag.

Test Execution Process

Execution Stages

  1. Initialization: Maeris prepares the test environment

    Browser launch, environment setup, variable initialization

  2. Pre-Test Hooks: Execute any configured "Before Each" hooks

    API calls, authentication, test data setup

  3. Test Steps: Execute each test step sequentially

    Navigate, click, type, verify actions

  4. Post-Test Hooks: Execute any configured "After Each" hooks

    Cleanup, data reset, API calls

  5. Result Generation: Compile results, screenshots, and logs

    Generate report, capture screenshots, save execution data

Understanding Test Results

Passed Tests

A test passes when all steps execute successfully and all verifications are met. You'll see a green indicator and can review the execution details.

Failed Tests

A test fails when a step cannot be completed or a verification fails. Common failure reasons include:

  • Element not found (selector issue)
  • Timeout waiting for element
  • Verification assertion failed
  • Application error or unexpected behavior

Skipped Tests

Tests may be skipped due to prerequisites not being met, conditional logic, or manual skip configuration.

Test Information Modal

The Test Information Modal provides comprehensive details about your test case, including configuration, execution history, and results.

Modal Sections

  • Test Overview: Basic information, description, tags, and status
  • Test Steps: Detailed view of all test steps with selectors and actions
  • Execution History: Complete history of all test runs with timestamps and results
  • Latest Results: Detailed breakdown of the most recent test execution
  • Screenshots: Visual evidence from test execution
  • Logs: Detailed execution logs for debugging
  • Configuration: Test settings, browser, environment, and timeouts

Result Details

What You'll See

  • Execution Time: Total time taken to run the test
  • Step-by-Step Results: Status of each individual step
  • Screenshots: Visual snapshots at key points during execution
  • Error Messages: Detailed error information for failed steps
  • Network Logs: API calls and network activity during test execution
  • Console Logs: Browser console messages and errors
  • Performance Metrics: Page load times and performance data

Interpreting Results

  • Review screenshots to see what happened at each step
  • Check error messages to understand why a step failed
  • Compare with previous runs to identify trends
  • Use logs to debug issues and understand test behavior

Viewing Execution History

Access the complete execution history for any test to track performance over time and identify patterns.

  • View all past executions with dates and times
  • See pass/fail trends over time
  • Compare execution times across runs
  • Access historical screenshots and logs
  • Identify flaky tests or intermittent failures

Best Practices

  • Review Results Promptly: Check test results soon after execution to catch issues early
  • Use Screenshots: Screenshots provide valuable context for understanding test behavior
  • Analyze Logs: Detailed logs help diagnose complex issues
  • Track Trends: Monitor execution history to identify patterns and flaky tests
  • Document Failures: Note common failure patterns to improve test reliability
  • Compare Runs: Compare current results with previous successful runs to identify changes

Next Steps

Now that you understand test execution and results: