Static Testing Techniques
Overview
In this tutorial, we will learn more about Static Testing Techniques. Various Software testing techniques are outlined here:
https://www.testingdocs.com/software-testing-techniques/
Static Testing Techniques
Static testing is a software testing technique that does not involve executing the code. Instead, it examines the code or other software artifacts without actually running the program. Static testing techniques help identify defects early in the development process, which saves time and money.
In this technique, software code is not executed. Software code and algorithms are inspected, and reviewed to uncover code-related defects and enhance code quality.
Types
Some commonly used static testing techniques are as follows:
- Static Analysis
- Walkthroughs
- Inspections
- Reviews
- Code Audits
Static Analysis
Static analysis is a technique that uses software tools to examine the code or other software artifacts to identify defects. The tools can check for coding standards violations, security vulnerabilities, performance issues, and other defects.
Examples: SpotBugs, Checkstyle, SonarQube, PMD, etc
Inspections
An inspection is a process of examining project artifacts( like design specifications, project plans, production lines, etc with the intent to identify defects or to find defective units. Inspections are carried out by trained individuals to identify defects using a well-defined process.
Walkthroughs
A walkthrough is a meeting session in which the organizer walks through a project artifact with the participants. The participants ask questions and make comments. The main aim of Walktrough is to discuss possible errors in the artifact. For example, the code walkthrough session.
Reviews
Reviews are a form of static testing where a group of people examines the software artifacts such as requirements, design documents, code, and test cases to identify defects. This technique can be done formally or informally, and the reviewers can be peers, stakeholders, developers, experts, etc.
Informal Reviews
Informal reviews are review meetings with no formal process or procedures being followed. These meetings are not documented.
Formal Technical Reviews
Formal technical review meetings are structured review meetings.
These are documented and MOM reports are sent to the meeting participants. The software team assesses the quality of the project artifact in the meeting.
Code Audits
Code audits are a type of software review where an experienced developer examines the code for defects and provides feedback. This technique is particularly useful for identifying defects related to code readability, maintainability, and performance.
—-
Software Testing Tutorials:
