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
      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.2.MarathonITE Projects

In MarathonITE you start testing by creating a project. A MarathonITE project is a folder in the file system. Various sub folders in the project folder holds differnt types of project resources.

Marathonite Project Folder
Marathonite Navigator Window

A brief description of project resources

MarathonITE supports checklists that can be inserted into the test scripts for semi automated tests and exploratory testing. This folder maintains checklists that you create.

Features and Stories
If you use BDD style grouping of tests, these folders keep the story and feature groupings.

MarathonITE fixtures allows you to prepare a well known state for each test script. You can also use a fixture to change the launch parameters for the AUT - or launch a different application all together.

The Modules folder(s) keep method definitions that can be reused within test scripts. Unlike the library methods available with ruby runtome, the Module methods are available for insertion while recording. You can organize module files in subfolders.

All test tests that you create are stored within the folder structure of TestCases folder. You can organize the tests within subfolders.

omap Folder, omap.yaml and omap-configuration.yaml
The omap-configuration.yaml maintains the current object map configuration. The omap folder and omap.yaml file maintains the object map being used by the project.

This folder is used for saving the test data in CSV format for data driven testing.

When you use TestRunner view or enable generate reports options, the generated reports are stored in this folder. Note that actual report is created only when you view the option as it is a costly operation.

If you link your tests to an Issue manager, the tests groping is stored in this folder.
The file contains the logging configuration. The default log level is warning, however you can change it to other values while debugging MarathonITE internals.

The project configuration is stored in project.json file.

When test scripts are executed, the generated console output is stored in a console.log file for the current session. Upto five files are generated and rotated for each MarathonITE session.

Suggest Edit
Close Menu