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

3.8.2.Executing Tests from Test Runner

You can run multiple tests in MarathonITE using the test runner view. You can open the test runner view by selecting multiple tests to execute.

Test Runner UI

Running Tests

Select the TestCases folder or multiple test cases from the Navigator view and open the context menu by using rightclick. Select Play option. MarathonITE opens a Test Runner view and executes all the selected tests. You can select test to run from TestSuites, Features, Stories, Issues views also.

Test Runner Play

Test Runner displays the elapsed time to run all the tests. Test runner's progress bar that displays the test case count, error count and failure counts. The progress bar turns to red from green if any one of the played scripts fails.

Test Runner Progress Bar

The trace section of the test runner view displays the stacktrace of a failed test script. Select a failed test script from the test case tree view to see the corresponding stacktrace.

Test Runner Failure

When you run tests from the Test Runner, checklists are always accepted and reports are always genearated.

Test Runner Actions

You can perform various actions using the test runner view toolbar.

Test Runner Toolbar

The following table explains each of the actions in detail.

Action Description
Next Navigates to the next failure from the tests.
Previous Navigates to the next previous from the tests.
Failures Toggle between all tests and failed test (tree-view).
Re-run Re-run the previous run test.
Re-run Stops the currently running tests. Note that Marathon waits for the current test to complete before aborting the test run.
Run Selecetd Runs the selected tests.
Report Generates and shows the report from current run.

Test Runner History

Test Runner allows you to save and manage test runs. Test Runner History is categorized into two parts Unsaved History and Saved History (Favourites). Unsaved History are remove as count exceeds Maximun Remembered Runs while saved history are saved forever and can be run any time by selecting the test, it can also be run from batch mode using name of the test (see section 3.8.3).

Test Runner Manage

Click on Manage History item from drop down menu. New window opens with list of unsaved test run history as show below.

Test Runner Unsaved

Unsaved History Actions
Action Description
Move to favourites Moves selected test run to favourites. It asks for a name, to save it (test run) with.
Manage Favourites Opens a window of saved test run (Favourites). On this window, you can manage saved test runs which is explained in below section.
Remove Removes selected test run from the list.
Clear all Removes all test runs from the list.
Max count Specifies the number of unsaved test runs to remeber.
Saved History Actions (Favorites)

Test Runner Saved

Action Description
Move Up Moves selected test run up.
Move Down Moves selected test run down.
Unsave Moves selected test run to unsaved history.
Remove Removes selected test run from the list.
Clear all Removes all test runs from the list.
Suggest Edit