What does static testing examine specifically?

Static testing specifically examines the software without executing it. This type of testing involves reviewing artifacts such as requirements documents, design notes, and source code to identify defects early in the development lifecycle. By analyzing these documents and by performing inspections, reviews, or static code analysis, it helps to catch issues before they can result in runtime errors. This proactive approach is crucial in agile environments where quick feedback loops are essential for ongoing development.

Dynamic performance of the software, design strategies, and overall system functionality all pertain to aspects of the software that require execution or operational testing, distinguishing them from the primary focus of static testing which is analysis without execution. This separation highlights the unique role that static testing plays in the overall quality assurance strategy.