Static tests are tests of a component or system at the specification or implementation level performed without running the software. Static tests seek to validate compliance with a set of rules through inspection of requirements and/or source code analysis.
Unlike dynamic tests, these do not require software execution to be performed. Part of the purpose of static testing is the review of work products such as requirements documents, test cases, test plans, code, user guides.
Different techniques are used such as:
Review the degree of maturity of the definition, specification and management of the software requirements.
The aim is to ensure a common understanding between the customer and the development team.
Recommendations are given on the following criteria:
The architecture and use of standards is verified in the design.
The aim is to detect and identify nonconformities and improvement aspects of the design before moving on to coding.
Identify non-conformities in the source code.
The goal is to detect and identify software anomalies, including errors and deviations from standards and specifications.
The developers are shown the benefits of using standards and how to avoid systematic defects.
It is defined from the set of criteria to evaluate and recommendations are generated for the development teams about:
Among the main benefits of Static Tests are:
Contact us
COLOMBIA
Carrera 85b N° 14 46
El Ingenio II
Cali – Valle
USA
1809 W Jetton Av 33606
Tampa Florida
