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

3.9.3.Organizing Tests in Suites

You can organize tests in MarathonITE using Test Suite. A suite is a generic grouping mechanism in MarathonITE. A suite can contain tests, features, stories, folders and also other suites.

A suite can not include itself either directly or indirectly.

Working with Suites

MarathonITE stores the suite information in files with extension .suite in Suites folder. The content is stored in JSON format.

Creating Suites

To create a new suite, select File->New->New Suite option from the menu.

Creating a Suite - Marathonite

MarathonITE displays a popup window. Provide the name of the suite and click on OK.

Naming a Suite - Marathointe

MarathonITE creates the new suite and opens it in the editor. The editor displays two panes. The left pane displays all the tests, features, stories etc. that are available and the right pane contains the list of tests added to the suite.

Suite Editor - Marathonite

Drag and Drop the tests into the suite. You can rearrange the order of tests by using the Up and Down buttons. Remove tests from the suite using Remove button.

Use Click button or Control+S (CMD+S on Mac) to save the suite.

Executing Suites

To execute all the tests in a suite, select Play option from the context menu. MarathonITE opens the Test Runner view and executes the tests.

Batch Running of Suites

You can execute one or more features using MarathonITE batch mode.

Reports in Suites

MarathonITE doesn't group the tests as suites in the reports because they are generic. Other grouping mechanisms are used to display the test organization.

Suggest Edit
Close Menu