Besides software testing, testers have a lot of different activities such as meetings, calls, e-mails, etc. It is necessary to distinguish testing procedure itself from other actions. Session-based test management helps to solve this problem.
Session is the separated scope of work done during testing procedure. Each session has its own purpose and problem that should be solved. If the session lasts less than 45 min, it is called a short session. A long session takes about two hours.
What Are the Main Session Tasks?
- Test design and its execution. The product is examined, and tester looks for any problems.
- Bug searching and reporting. If the problem is found, tester makes sure that it really is a bug and makes the necessary reports.
- Session setup. Tester configures tools, writes reports, reads documentation, etc.
These activities are often called the ‘TBS’ metrics. It is the basis of testing procedure. Every testing type, for example, system testing, functional testing, load testing, etc., contains such tasks.
Tester should estimate the approximate time needed for each of these tasks including time spent on opportunity. Opportunity testing contains the tests that are out of the session charter. If tester notices the serious off-charter problem, he should focus on this particular problem diverting from the charter.
What Are the Key Elements of the Session Sheet?
- Bugs (show the product quality).
- Issues (problems related to testing procedure).
- Notes (contain the ideas of test cases, function and risk lists, etc.).
There is a certain structure of the session report. It should contain some obligatory points.
What Are the Components of the Session Report?
- Session charter (including goal setting)
- Tester’s name
- Date and time of the beginning
- TBS metrics
- Bugs found
Each of these points should be checked. With the help of the tool written in Perl, the session sheet is scanned. The results of scanning are shown in the form of table that can be easily analyzed and formatted. It is the ToDo session sheet or the so-called the ‘hopper’ list. After checking some issues with the help of functional testing, the specialist fills the table and starts to perform another testing type, for example, usability testing. It provides the execution of testing procedure step-by-step without missing anything.
Moreover, the hopper helps to cooperate with clients and perform their different requests. Testers make an appropriate note in the hopper. They mark the request with the priority defined by the client.
The search utility is intended to make the use of session sheet more convenient. It enables to display and print any part of the session sheet.