Improving quality with short-term/intensive and low-cost ad-hoc testing
The disadvantage of general ad-hoc testing is that it is susceptible to individual viewpoints and experience. In addition to the general approach to ad-hoc testing, SHIFT utilizes “unique testing perspectives” that have been standardized based on past knowledge. Since we are well-versed in detecting problems, we can efficiently improve quality even when there is a tight deadline.
We conduct short-term and concentrated ad-hoc testing on systems about to be released to identify important issues that would be too late after release. We can also provide materials on decision-making for releases, including analysis of problems identified during ad-hoc testing, decisions on whether quality enhancement measures need to be adopted, and presenting the content of enhancement tests.
01
When conducting ad-hoc testing, SHIFT assigns dedicated members that can perform real-time decisions on the areas for conducting tests and managers that understand the system properties of each industry. This enables catching up in a short amount of time regarding the system properties and contributes to early identification of important problems and the planning of quality enhancement measures.
02
Ad-hoc tests conducted by specialist teams analyze the failure detection rate of each project from the standard test perspectives held by SHIFT, including the test perspectives of ad-hoc testing. We also continuously implement the PDCA cycle to improve the failure detection rate.
03
We identify items that are not normally tested by regular development companies and adopt “worst-case scenario” testing from the user’s perspective. We also systemize the preconceptions of developers and tacit knowledge unique to the project to discover problems that are difficult to detect in regular testing from a third-party perspective.