1. Preface
    1. About MarathonITE
    2. Supported Platforms
      1. Java/Swing™
      2. Java/FX™
      3. Web Applications
    3. What's New in MarathonITE 5.0
    4. Change Log a.k.a Version History
    5. System Requirements
    6. Copyright Notice
  2. Getting Started
    1. Introduction to Test Automation
      1. Unattended Testing
      2. Semi Automated Testing
      3. Exploratory Testing
    2. MarathonITE Projects
    3. Your First Project
      1. Java/Swing™ Test Project
        1. Application Under Test - SwingSet3
        2. Creating a Project
        3. Recording a Test
        4. Anatomy of a Test Script
        5. Running Tests
        6. Looking at Results
      2. Java/FX™ Test Project
        1. Application Under Test - Ensemble
        2. Creating a Project
        3. Recording a Test
        4. Anatomy of a Test Script
        5. Running Tests
        6. Looking at Results
      3. Web Application Test Project
        1. Application Under Test - DuckDuckGo Search
        2. Creating a Project
        3. Recording a Test
        4. Anatomy of a Test Script
        5. Running Tests
        6. Looking at Results
    4. MarathonITE Sample Projects
  3. User Guide
    1. Installation and Startup
    2. MarathonITE User Interface
      1. Views
      2. Editors
      3. Output Views
    3. Creating Marathonite Test Projects
    4. Recording Tests
    5. Managing Checklists
    6. Exploratory Tests
    7. Semi Automated Tests
    8. Executing Tests
      1. Executing a Test from Editor
        1. Debugging Scripts
        2. Using Script Console
      2. Executing Tests from Test Runner
      3. Executing Tests in Batch Mode
    9. Organizing Tests
      1. Organizing Tests in Folder Heirarchy
      2. Organizing Tests as Features and Stories
      3. Organizing Tests in Suites
      4. Linking Tests to TMS and Issue Manager
    10. Modularizing Test Scripts
      1. Module Methods
      2. Extract Method Refactoring
      3. Using Data Loops
      4. Convert to Data Loop Refactoring
    11. Data Driven Tests
      1. Convert to DDT Refactoring
  4. Advanced Scripting
    1. Ruby Programming Language
    2. Marathon and Ruby
    3. Selenium/WebDriver Bindings
      1. Java/Swing™ Components
      2. Java/FX™ Controls

2.3.1.6.Looking at Results

When you execute the test script from the editor – the results are shown in the Results section of the window. Each entry contains the message, the file name and the location of the error. Doubleclicking on an entry opens the file and positions the cursor at the failing line.

By default, MarathonITE doesn’t generate a report for a test run from the editor. You can change this behavior by toggling the Marathon -> Generate Reports menu option. When you run a test script when this option is selected, you can look at the report by clicking on the Show Report button on the toolbar.

Marathon Report

When the tests are executed using the test runner, the results are shown with a success/failure indicator. When you select a test, the Trace section of the Test Runner view shows the stack trace if any of the failed test. Doubleclicking on a stacktrace entry opens the corresponding file and positions the cursor at the failing line.

MarathonITE always generates a report for the test runs from the test runner view. You can click on the Test Runner‘s toolbar button Show Report to see the report.

When the tests are executed using batch mode, MarathonITE generate reports in marathon-reports folder. You can change this folder using --report option of the command line.

MarathonITE uses Allure Reporting framework. The reports are generateed are rich and use HTML/CSS/Java script. While opening a report works in Mozilla Firefox™, it doesn’t work with all the browsers.

You can use allure-commandline package to see the report. A copy of which is distributed in allure folder of installation. Following command opens a report in the default browser.

Suggest Edit