Which statement is true about static testing?

Static testing is a method that focuses on reviewing and analyzing the software artifacts without executing the code. This can include techniques such as inspection, review, and static analysis, which allow testers to identify issues early in the software development lifecycle.

The true nature of static testing is that it evaluates documents, requirements, code, or any other artifact in a non-execution environment. This process is crucial because it allows teams to catch defects early, which is typically more cost-effective than finding them later during dynamic testing, where the software is executed.

The other statements do not accurately represent the essence of static testing. For instance, execution of the test object is a fundamental part of dynamic testing, not static testing, and while tools can aid in static testing, they are not a mandatory requirement. Lastly, static testing is not about finding defects that were previously identified during dynamic testing; instead, it aims to discover potential bugs before the software is even run.