What does static testing examine specifically?

Static testing specifically examines the software without executing it. This approach is designed to identify defects and issues early in the development process by analyzing documents, requirements, code, or other artifacts. Techniques such as reviews, inspections, and static analysis tools are utilized to ensure that the software meets specified requirements and standards prior to runtime.

In static testing, aspects such as coding standards, design flaws, and potential security vulnerabilities can be evaluated effectively without running the software. This method provides an opportunity to detect issues before they escalate into more expensive problems later in the development lifecycle.

The emphasis is on assessing the quality of the software’s artifacts during the development phase, allowing teams to address issues proactively, thereby improving overall software quality. This approach contrasts with dynamic testing, which involves executing the code and examining its behavior during runtime.