The document discusses the significance of static testing in software testing, emphasizing its role in identifying errors early in the development process through methods like walkthroughs and inspections. A case study illustrates how static testing contributed to a human resource development project, resulting in zero rework and high client satisfaction. Ultimately, static testing enhances product quality and efficiency by addressing requirements and issues early on.

1. Importance of Static testing in software
testing.
Static testing- Is a process of testing an application without actually executing it. It includes
Walkthroughs, inspections and reviews of docs associated with the application under test. Static testing is
the part of verification process. We can refer the case study below.
Importance of Static testing-
 Static testing can find errors which can be more lethal in the later stages of testing.
 Static testing prevents fault multiplication by identifying them in initial stage.
 Static testing helps to find errors and faults in the requirements itself if any.
 Static testing minimizes the effort of fixing those bugs which should actually be
addressed while the time of documentation.
Case study for static testing and its importance.
Here we will look up to a real time scenario (part of a project) which actually encounters the use
of static testing and in the course of development we (development and QA team) came to know
about the importance of Static testing.
Overview of the project- Project was about human resource development with all general
functionalities such as employee detail management, Leave management, Salary management,
Logins for different roles and there respective dashboards etc.
Documents provided for test basis-
 Requirement docs(SRS) by client.
 These docs were converted in to user stories and being depicted as BPMN by Business
Analysts.
Responsibility of tester-
As a tester the guy has now to verify the BPMN’s against the requirements and should report the
mistake to the BA.
Apart from this each block of BPMN is considered as a use case and tester has to make sure that
this shouldn’t be missed. After identifying all use case tester need to frame test cases using all
test case designing techniques and get it reviewed and approved.

2. How static testing helped in above mentioned case?
 It helps to attain zero rework as both the teams(offshore and onsite was on same page all
phases of development)
 Helped to attain zero requirement and specification related issues.
 It gives more time to the tester to concentrate on core functionalities and break them.
 Delivered a high quality product with huge degree of client satisfaction.