Skip to main content

Exploratory Testing

So far, in this tutorial we have

  • manually invoked a GitHub workflow to publish pre-canned results
  • implemented and executed new test specs from scratch
  • learned how to generate and manage GitHub issues in conjunction with a Project Board
  • formally defined a test session consisting of a set of specs for testing a build

This section of the tutorial will now focus on a different type of testing - Exploratory.

Exploratory testing is a test flow that provides additional test coverage and usability assessment, using a non-scripted testing approach.

Exploratory testing is non-scripted, no-constrained observational-based testing.

There are two variants of exploratory supported by Testspace:

  • Spec based observations
  • Session based observations

Both types are integrated with GitHub boards to support discussions and collaboration.

Let's do some exploring.

Setup Board#

Note that if you have already setup a GitHub Project Board skip this section.

To create a GitHub Project Board for Testspace, use the following steps.

  • In your testspace.getting-started repo, from the Projects tab click New project and use Testspace for Project Board Name
  • From the project template choose one of the three supported templates:
    • Basic kanban
    • Automated kanban (Recommended)
    • Automated kanban with reviews

Once the board is created go ahead and delete the 3 auto-generated notes - Welcome to GitHub Projects, Cards, and Automation.

Your board should look like the following:

Testspace Board

Spec Observations#

In Testspace, click on the main space of the project associated with your repo. Next, select the Manual tab to display a listing of all available specs.

Now go ahead and double click on the Hello Manual spec.

  • Select the START button to begin execution
  • Select Passed for the status of Test Case One
  • Select Passed for the status of Test Case Two

Now click on Observations, located at the bottom left of the spec dialog:

  • Add comments or images
  • In the ISSUES row, go ahead and change Do not report to Push new issue
  • Modify the Issue title if desired

Spec Observations

When done select the STOP button and close the Spec dialog when complete.

Testspace will automatically generate an Issue to be further discussed and managed on the Project Board.

Spec Observations Issue

Session Observations#

Now let's create observations for a Test Session.

Note that multiple testers can add their observations to the same test session.

Create a Test Session by clicking on the "New Test Session" button.

From the New Test Session dialog:

  • Add a name for the session - e.g. build.42.0a
  • Add an optional description (e.g. Provide feedback on beta features)
  • Click on the Exploratory checkbox in the right corner
  • Select SUBMIT

New Session

Once the Session is created a built-in Exploratory session spec will be provided.

New Session with Exploratory

Go ahead a click on Exploratory.

  • select START
  • Add comments, images, etc.

When done click on the STOP button.

Active Exploratory Session

The Exploratory session can be executed by multiple users. All of the observations will be automatically added to a GitHub Issue, named after the session, and automatically placed on the GitHub board.

Session Observations Issue

Recap#

Testspace supports Exploratory testing using both Spec observations and Test Session observations.

  • Running a spec a tester has the option to provide observations along with Issue generation
  • A Test Session can contain observations by multiple testers and is automatically managed on a Board
  • A Project Board is used for managing the ongoing discussion of observations with other stakeholders