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
      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.3.Exploratory Testing

Discovery. Investigation. Learning. These are the three main aspects that Exploratory Testing emphasises. The most prominent characteristic is that the Test Cases are not created in advance; testers check the system on the fly. The focus of exploratory testing is more on testing as a “thinking” activity. During testing, the tester learns about the software, its use, its strengths and its weaknesses.

Exploratory testing was defined as "a style of software testing that emphasises the personal freedom and responsibility of the individual tester to continually optimise the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.” by Cam Kaner, who coined the term back in 1984.

There are no hard and fast rules regarding the steps in which Exploratory Testing is done. In general, most of them have the following features:

  • Step 1: Create a Test Charter

    Exploratory Testing does not mean no documentation. Make a list of the following basics:

    Scope and Approach: High-level description of the system, components and functionality that need to be tested.
    Expected results
    Method for recording tested cases and results

  • Step 2: Set a Time-frame

    A deadline to work within will help the tester focus.

  • Step 3: Log as you execute

    Log test cases and results as you test. Logging creates audit and reference for your efforts. This can be helpful when you want to go back and review individual scenarios.

What should your Output be?

  • List of test cases and outcomes – including screen capture or videos of each test case
  • A report with key findings and recommendations.

There are several advantages to Exploratory Testing:

  • Faster discovery of major bugs
  • Decreased lead time for beginning testing
  • Most importantly, testing normally untested parts of the system, and therefore discovering hidden bugs that can cause a lot of heartburn.
  • This testing is useful when requirement documents are not available or partially available
  • It involves Investigation process which helps find more bugs than normal testing
  • Uncover bugs which are normally ignored by other testing techniques
  • Helps to expand the imagination of testers by executing more test cases which finally improves productivity as well
  • This testing covers all the types of testing and it covers various scenarios and cases
Suggest Edit
Close Menu