Reactive testing is when testing is not started until after design and coding are completed. The QA team is the owner of this type of testing. In this series of Embold for QAs, we will be going through all the ways in which Embold can be used in reactive testing.
1. Identify bug-prone components
The Embold risk score signifies the urgency of addressing a component for testing. The Embold risk score ranges from 5 to 1, where 5 represents high risk and 1 represents a low risk. Risk score considers frequency of changes, the number of issues and severity of issue tickets raised against a specific component (or class)
Vulnerabilities & Code Issues
A vulnerability detected can mean system more prone to external attacks. It is important for the QA to explore these vulnerabilities immediately.
Critical code issues like memory utilisation need to be tested and fixed on priority else it might result in system crash.
Changes view helps you see the difference between two versions of your source code. Knowing the changed components can help narrow down test scope.