@dila Yes, I produce session reports on a daily basis for all my test sessions, which usually last between 2 and 3 hours. There are cases when my sessions are shorter, for example for a charter like “Re-test the 2 bugs fixed on 28/04/2021”. Something like this can take 30 to 60 minutes.
On a typical day I produce two session reports. It is the way I make explicit what and how I’m actually testing and the reports are my go-to in the event of an audit of testing.
It may seem like an overhead, but after some practice it will not take more than 15-20 minutes to write the report. Optionally, you can track this time under “Setup and admin” and include it in the session duration. You can get some metrics after writing a few reports and they can help you estimate the time it would take you to test and report new features or similar applications. These metrics can also help you improve the process:
-
tester spent most of the time on bug investigation? - this interrupts hunting for bugs and impacts testability
-
tester spent most of the time on test execution? - what new, interesting did they learn
-
was the majority of the session spent on setup? - this may indicate testability problems; why did it take so long?
This is a good article to read. It’s quite old but it is what got me into exploratory testing and session based test management. Session-Based Test Management - Satisfice, Inc.