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.10.1.Module Methods

Marathon modules are regular ruby modules – except that Marathon interprets them to provide access to them during recording scripts. Each module is a script file within a module folder. Each file can contain one or more methods.

A test project can have multiple Modules folders. When you create a project, Marathon creates a default module folder Modules. The Modules folder is added to the language runtime path, so that you can access these files from the test scripts.

Creating Module Folder

For creating a module folder use File --> New --> New Module Directory, Marathon opens a New Module Directory dialog.

Creating a Module Folder

Creating submodules

Use Navigator view to create a folder. These folders will be avilable as submodules in insert script command.

Creating Module Function

Module Files : A module file is a script file with one or more methods. Marathon interprets these methods.

A method can have default values for parameters. When inserting, these default values are shown in the Insert Script dialog. If the default parameter is a list, then Marathon displays true/false combo box.

Creating Module Method

Using File --> New --> New Module command you can create a templet for a module method. When you select this option, Marathon opens a New Module Function dialog.

Creating a new Module Method

Module function name : Enter a name for the module method. This should be a valid method name according to the script syntax.

Description : Enter a description for the module method. This will be written into the module file and also displayed when insert script command is executed.

Module Directory : From the drop-down list, select a module directory.

Module File : You can select the name of an existing module file or enter a new module file name here. If the file already exists, Marathon appends the method template to the module file.

Click OK to save the method template. Marathon saves the template into the file given and positions the cursor inside the method.

Suggest Edit