Testing - Testing session
Last modified on Mon 30 Jan 2023

Alone we can do so little, together we can do so much. — Helen Keller


The testing session is an event you can integrate into your process of releasing a mobile or a web app. The idea is to create a meeting with colleagues from the project you are working on and test as a group. You can invite all team members - developers, designers, testers, and your project manager. If the clients are up for it, you can invite them as well.

Testers execute regression tests on most projects to check if everything works as expected before the production release. Test docs are often used to guide those regression tests. Testing sessions are not meant to replace those scripted regression tests, they are a supplementary process.

Benefits of testing sessions

There are a lot of benefits to organizing a testing session with your project team:

Basic steps

  1. Explain the purpose and benefits of a testing session to your project team.
  2. Create a calendar event for the testing session.
  3. Prepare a test plan.
  4. Make a small introduction for the app/features that will be tested.
  5. Test the app during the testing session.
  6. Collect all the issues that were found and open tasks in your project management tool.

What is your role?

A tester that organizes the testing session event is also a moderator. Make sure to:

Creating a test plan

The organizer should create a test plan for all the participants of the testing session.

A good practice is to divide the application by features or specific parts which need to be tested and then allocate every part to a participant of the testing session. The test plan should include:

Later on, when the time is up and the bugs you all found are on the list, the moderator should create a task for every bug in the project management tool (Productive, Jira, etc.).

You can find the template for the testing session here. Feel free to copy it and use it for your project.

General tips for the testing session