Team Handbook
Role guides for TechAbout teams, including responsibilities, growth paths, skills, and day-to-day operating expectations.
Public
QA Engineer Team - Testing Software Development
Use this guide for the QA Engineer Team. It sets clear expectations for responsibilities, handovers, growth, and day-to-day work.
Guidance
4.1 Why testing is needed
- The purpose of software testing is to ensure that the software does exactly what the user needs it to do, ensuring quality.
- It can be used to check that the software is functioning correctly, reliably, efficiently, securely and is usable.
- Errors in software as a result of non-testing or inefficient testing can cost a business money, time and reputation.
4.2 Stages of Software Testing
4.3 Different Types of Testing
There are many different types of testing and we will focus on the following:
- Acceptance Testing
- Black Box Testing
- Functional Testing
- Graphical User Interface Testing (GUI) – Usability Testing
4.4 A Testing Checklist
This should check the following:
- Have all aspects of the software that has been developed has been tested?
- If any tests have failed, have they been redone and passed?
- Is the Test Plan structured correctly?
- Is the Test Report structured correctly?
Updated on 6 July 2026
Need a team guide updated?
Tell us what is missing or unclear so the responsible team can update the guide.