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.1.2.Semi Automated Testing

When we automate tests, we often find that there are cases that require manual intervention to decide the success/failure of a test case. There is still a place for manual testing with tool assistance in our projects. Semi automated tests falls in between the fully-automated tests and manual tests. We use the tool to perform operations that can be automated, leaving the some of the verification process to the manual tester.

Test Cases that can be semi automated

  • Look and Feel
    We often need to check the look and feel of an application. We can use automation to ensure that we reach each of the application windows and perform actual verification manually.
  • Checking for Organizational Standards
    Similar to the Look and Feel tests, we may want to check whether the UI is following our organizational standards. In MarathonITE we can create a checklist listing our standard and then use semi automated tests to insert the checklist to create our report.
  • Non deterministic output
    When the output from our test case is non-deterministic, it is almost impossible to create a automated test. Semi automatic tests can be used in these cases.

Avoid these cases

  • Synchronizing between two applications
    There are cases where our test depends on the output from another application. It is still better to automate the whole test (though difficult), than keeping it semi automated.
  • Processing output from the application
    In cases you need to operate on the output of the AUT to decide the status of a test script, it is better to automate the test.
Suggest Edit