Static Tests

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:

Informal review

Technical review

Guided review


Code review

Static Testing can be performed at any stage of the software lifecycle, but is most effective when performed early, when the code is still relatively new.

Types of Approach to Static Tests

Requirement Reviews

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:

  • Identify functional and nonfunctional requirements
  • Guarantee the quality of the definition and specification of requirements
  • Management requirements in the development cycle
  • Maintenance practice of the product roadmap
  • Change control administration
  • Mechanisms to measure requirements

Design Reviews

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.

Code Inspections

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:

  • Programming logic
  • Coding standards
  • Coding documentation (Headers, Comments)
  • Imports
  • Initializing
  • Calling method parameters
  • Use of nesting structures
  • Modularity
  • Code reuse mechanism
  • Error management

These tests focus on the prevention of defects and their early detection, since they can be carried out at any stage of the software life cycle according to the information that is available.

Benefits of Static Tests: :

Among the main benefits of Static Tests are:

  • Satisfied customers

    By having the requirements well defined, the re-processing and associated costs are reduced due to misunderstandings or because something was not defined. Customers are more involved in the development process.

  • Measure to improve

    Static code analysis tests allow to obtain measurements of the maintainability of the developed software, together with compliance with norms, standards and good practices.

  • Take care of the identity of the company in the market

    It allows mitigating the risks associated with releasing products with defects. Customer confidence in products and services is improved.

  • Take care of the IT identity in the company

    IT areas improve their identity with their internal customers, by providing software aligned to defined requirements and deadlines

The objective of all our TESTS is to validate that the software fulfills the required quality level to go into production.

Do you want to know more about this service?

Contact us

Carrera 85b N° 1446
El Ingenio II
Cali – Valle

1809 W Jetton Av 33606
Tampa Florida

WhatsApp GreenSQA
Enviar Vía WhatsApp