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.7.Semi Automated Tests

It is not possible to automate all test scenarios in any given test project. There are always tests that need manual intervention and subjective validation. It is still possible to use automation for simplify these tests.

MarathonITE facilitates such Semi Automated tests through checklists. You record a normal test. When the application reaches a point where you need a manual validation, insert a check list. You can continue recording the test. You can also add more than one checklist per test script.

These tests are also executed as normal tests. When the point of execution reaches a inserted checklist, MarathonITE pauses. MarathonITE displays the checklist. Once you fill the checklist – the execution of the test continues.

1. Use Cases for Semi Automatic Tests

The following are some cases where semi automatic tests will be very useful.

  1. To check whether the application is following guidelines for UI
    Most organizations have user interface guidelines. Checking whether the application follows all guidelines is a monotonous job. Over a period of time it becomes tedious. Semi automatic tests can help you simplify this process of verification. Start with converting the guidelines into a checklist. For each of the application screen, create a script that opens up that screen. Insert the guidelines checklist into the script.
    When executing these tests, Marathonite performs actions as with regular scripts. When the application reaches the screen, Marathonite displays the checklist. The tester can verify each field for confirming to the guideline. In case of an issue, the tester can mark the test as failed. He/She can also capture a screenshot and annotate it.
  2. To check the validation criteria of fields
    Automating tests for field validations is tedious and in some cases impossible. Some field validations do not allow the application to proceed further. Some others may not even allow submitting a form.
    We designed semi automatic tests to handle these cases. Create field validation checklist for each of the screens and attach them into a test script.

2. Creating a Semi Automated Test

Inserting a Checklist - Semi Automated Tests

You create a Semi Automatic test by following the same recording procedure as it is for a normal test. Reach the point in application where you need manual intervention. Insert a checklist by clicking on the insert checklist button. MarathonITE shows a Select a Checklist dialog.

Select a checklist from the available checklists and click on Insert button. MarathonITE adds the checklist to the script using accept_checklist command.

If required, perform more operations and insert checklists at the points you desire. At the end, stop the recording using the stop button.

3. Running Semi Automated Tests

By default, Marathonite ignores the accept_checklist commands in a test script. For running tests that accept checklists, enable the option Enable Checklists from the Marathon menu.

You can execute the semi automated tests either from the editor, the test runner view or using batch mode.

Marathon pauses the script and displays the checklist when it reaches the accept_checklist command. once you fill the checklist and save it, the script continues. The report displays the information you enter in the checklists.

Suggest Edit