What is Static Testing?

• A. Testing of software code via analysis of the code; also known as white box testing.
• B. Testing by executing the software with real data.
• C. Testing for performance benchmarks.
• D. Testing the user interface for usability.

Answer: (A)

Static testing focuses on examining software artifacts without running the program. It involves reviewing the source code, designs, and requirements, and using automated tools to analyze the code for issues such as defects, security flaws, and coding standard violations. Because the program isn’t executed, defects can be found early in the development process, saving time and effort later. This approach aligns with white-box testing in that it uses knowledge of the internal structure of the code to identify problems. The other activities described—executing the program with real data, measuring performance, or evaluating the user interface for usability—require running or interacting with the software and then fall into dynamic, performance, or usability testing, not static analysis.