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.4.Anatomy of a Test Script

In this section we have a quick look at the recorded test. By the time you finish recording the earlier test, the editor should have the following recorded test:

  1. require_fixture
    The require_fixture statement within the marathon marker block, identifies the fixture to be used for running the test script. You can have multiple fixtures in your project – each one differing either by the way the application is launched or by setting up test environment.
  2. test method
    All MarathonITE test scripts have test entry point. This is the entry point for the test and executed after the fixture setup method.
  3. select
    select is MarathonITE‘s main method for setting the state of a component. This method takes an object name and a value in most cases. The object name is used to look into the object map to find the recognition properties and the state of the object is set using the value.
  4. click
    click does what you expect it to do.
  5. assert_p
    MarathonITE uses assert_p to add a check point to the script. The parameters are the object name, the property and the expected value.
  6. with_window
    with_window sets the top level context in which the other statements need to be executed. MarathonITE changes the object map context to the given window name as well as informing the Java driver (the selenium/webdriver for Java applications) to switch_window.
Suggest Edit