What is one of the principles of static testing?

One of the principles of static testing is that it includes the evaluation of analysis and design documents. Static testing is a form of testing that involves reviewing and analyzing project artifacts without executing the code. This can encompass various types of documentation, such as requirements specifications, design documents, and even test plans.

By examining these materials, static testing aims to identify defects early in the development cycle, allowing for corrections before the code is even run. This proactive approach can save time and costs by catching issues related to functionality, consistency, and compliance with standards early on. Static testing techniques include reviews, inspections, and walkthroughs, making it a valuable method for ensuring quality from the outset of the software development process.

The other options provided do not align with the principles of static testing. For instance, executing code is not a requirement for static testing, and it is not limited to developers, as testers and other stakeholders can also engage in these activities. Furthermore, while static testing aims to find defects, it does not guarantee complete test coverage of all code or scenarios.