Skip to main content
Test Session Testing

What is Test Session Testing and how does it work?

Evgeniya Graich avatar
Written by Evgeniya Graich
Updated over a week ago

In Test Session Testing, you document the time you spend testing a given product. This process is similar to any exploratory test on the test IO platform. We use this feature to demonstrate to our customers the amount of spending testing time. To ensure the data is accurate, only activate the Test Session for the time you actually spend testing.

The Test Session activation is a mandatory requirement to start testing products. You can only submit bugs once you've started your Test Session. You can see the Test Session bar at the top on the Test Overview page, and in order to start your Test Session, simply click the record button on the right:

In the "New Test Session" window from the drop-down menu, select the amount of time you plan to spend testing. The "Annotations" field is optional, you can use it to specify details such as the specific testing methodologies you intend to use or your testing focus.

The maximum duration for a Test Session is 4 hours. You can select the estimated testing time from the drop-down menu.

Once you click the "Start session" button, your Test Session begins, and the options to submit bugs become available until the session ends. You can now start testing the product.

The remaining time for your Test Session is displayed on the Test Session bar:

If you need more time to complete your testing and reporting the bugs, you can extend your session as long as the test is still ongoing. To do this, simply click the "Extend Test Session" button on the Test Session bar:

In the "Extend session time" window, select how much additional time you need and briefly explain the reason for the extension (in no more than two sentences):

If you finish testing earlier than planned, you can stop your Test Session via the Test Session bar. In the "Annotations" field, provide any helpful feedback about your testing experience. Here are some questions to guide your feedback:

  • What approach did use to find new bugs?

  • Did you test all features or were you selective, and why?

  • Which of the following activities did you focus on: bug reporting, Reproduction submissions, User Story executions, and why?

  • What is the main reason for you ending your Test Session?

  • Did the test match your expectations? Why/why not?

Remember! You can only have one Test Session active at a time. To start a new Test Session for a different test, you must end the current one first.

Did this answer your question?