A Guide for Test Engineers Test engineering leadership involves making sure software is of high quality and meets the needs of the end-user. One approach to achieve this is through session-based test management. Session-based test management is a testing method where specific goals are set and progress is measured over time. The focus is on working with other teams and continuously improving the testing process.
This leads to better collaboration, more efficiency, and higher-quality software. To implement session-based test management, test engineers should start by setting clear goals and objectives for each testing session. These goals should be agreed upon with other teams, such as development, product management, and customer support, to ensure that testing is aligned with the needs of the end-user.
Next, test engineers should measure the results of each testing session using metrics and data, and track progress over time. This information can be used to continuously improve the testing process. Working closely with other teams is also essential for the success of session-based test management. Test engineers should collaborate with other teams to ensure that testing is aligned with the needs of the end-user and that the results of each testing session are being shared and discussed.
In conclusion, session-based test management offers test engineers a structured and collaborative approach to testing. By focusing on continuous improvement and collaboration with other teams, test engineers can ensure high-quality software that meets the needs of the end-user. Whether you are a seasoned test engineer or just starting out, session-based test management is a valuable framework for success.
A test session is a period of time during which a person performs testing. A test session is focused only on testing activity. Sessions allow us to differentiate between testing time and everything else so that we can develop an accurate picture of the testing effort.
Testing activity, in a session, can be broadly categorized into three task categories:
- Test Execution (T time) is the time when the tester is actively hunting for bugs or otherwise doing any activity that has a reasonable chance of uncovering a bug.
- Bug Investigation & Reporting (B time) is an activity in a session focused on investigating and reporting a specific bug, that interrupts the course of test execution.
- Setup & Administration (S time) is any activity in a session that is required to satisfy the charter, but which interrupts bug finding and bug reporting. Setup and admin activity includes test design, equipment configuration, reading documentation, writing session reports, etc.
- A test session is the basis of measurement in SBTM. We use these task breakdowns to derive Task Breakdown Metrics for every session. To derive accurate measurements, it is important to focus session time only on activities that fall into those three task categories. In the session report, the tester records the length of the session and estimates the percentage of session time they spent on each type of task.
