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.6.Exploratory Tests

Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, test design and test execution.

Exploratory testers often use tools to record the session. These tools include screen capture or video tools. They also use tools to analyze output, environment etc. to generate interesting cases.

MarathonITE provides an exploratory mode of testing. During an exploratory test, MarathonITE records the steps in the background. You can also include checklists, notes. MarathonITE allows you to capture screenshots and annotate them.

1. Starting an Exploratory Test

You start exploratory testing in MarathonITE by using File -> New -> Exploratory Test menu option. You can also use the keyboard short cut Ctrl+Shift+N to start an exploratory test.

When you start an exploratory test, MarathonITE creates a new file for saving the actions. MarathonITE also starts a recording session. While you exercise the application, MarathonITE records the actions in the test script.

2. Recording Findings with Checklists

Marathonite Control Center - Insert Checklist command

If you want to record a finding, use the insert checklist command from the Control Center window.

Explorary Testing - Inserting a Checklist - List of Checklists

Marathon displays Select a Checklist dialog, select a checklist and click on Insert command.

Filling up a Checklist while Exploratory Testing

Marathon opens the checklist in a separate dialog. From this window, you can fill the checklist. After filling the checklist, click on Save to save the checklist into the report.

In most cases you may want to use Note and Screenshot checklists during the exploratory testing. You can also create your own checklists for using with exploratory testing.

3. Attaching a Screenshot

Capturing a Screen while exploratory testing

You can attach a screenshot of the screen to the checklist by using Screen Capture button. When you select the command, MarathonITE opens Screen Capture Annotation Window.

The annotation window displays the screenshot on the left and a list of annotations to the right. For adding an annotation, use the mouse and select an area on the image. MarathonITE highlights the area selected and adds an empty annotation entry. Type any free form text into the notes area.

Finally, save the screenshot by clicking on Save button.

4. Finishing Test and Sharing Results

You stop the test by using the stop button. Once the test is stopped Main window will display the recorded script in an editor. A report is generated and saved in the TestReports folder. The report is shown in the main window.

The test script itself is saved under Exploratory Tests folder within TestCases folder. The file is named with a prefix of “et-” and a timestamp.

Every exploratory test run creates a report and is saved in the TestReports folder. The index.html file in the reports directory is an HTML report for the test run. All resources referred by the report are also saved in the same directory. For sharing the report, just share that directory. You may also share the test script to show the steps performed.

If you want to share the script, the whole project structure should be replicated on the other machine.

Suggest Edit