Static Testing Methodology
Static testing is time consuming and can be costly, and it requires complete buy-infrom the management team.
Static testing > Better Documentation > Better Code > Fewer Defects > Faster Delivery > Higher Quality > Happier Customers
Static Testing Methods
Formal software inspections involve peer reviews of parts of the application that have been fully designed and documented. This is the most formal and time-consuming method.
The application or module is analyzed to ensure that it meets the business needs.
This method helps to find anomalies, consider alternative approaches, and evaluate conformance to business or industry standards.
How Static Testing is Performed
Used to validate that all end-user actions are identified, as well as any input and output related to them.
This checklist makes sure that the Functional Requirements identify all necessary elements such as constraints, calculation methods, and user characteristics.
This document looks for matches to the use cases and requirements and verifiesusability.
This checklist verifies that every field in the UI is defined well enough to create field level validation test cases.
With this checklist, the architecture is reviewed for completeness and clarity.
Static ROI Calculation
- Calculate total # of hours spent static testing
- Convert those hours into a dollar amount – this is the amount of money invested in static testing
- Convert the # of defects found in static testing into the number of hours that would have been needed to fix them if they had been found in traditional testing (1 defect = 10 hours to fix/test traditionally)
- Convert number of proposed hours fixing/testing defects into a dollar amount that would have been spent
- Subtract the amount invested in static testing in step 2 from the proposed amount calculated in step 4 to see the amount saved by static testing