Static testing includes:

Static testing is a software testing technique that involves examining the code, requirements, or other project documentation without executing the software. This type of testing is conducted to identify potential errors, ensure quality, and conform to standards early in the development process.

The correct answer involves code reviews, which are a form of static testing where developers review each other's code for defects, coding standards, and best practices. This process occurs before the code is executed, making it part of static testing. It allows teams to identify issues such as coding errors, logic flaws, and adherence to design specifications, all crucial for improving the quality of software before it goes into dynamic testing phases.

In contrast, unit testing, integration testing, and system testing all involve executing the software to validate that the code behaves as expected or meets specified requirements. These types of testing are concerned with dynamic analysis, where execution of the software is essential to uncover defects. Thus, they do not fall under the category of static testing, which focuses purely on non-execution reviews of various artifacts.