In the context of code standards, which statement about unit testing is most accurate?

• A. It verifies the behavior of the entire system under production-like conditions
• B. It focuses on performance optimization of modules during development
• C. It verifies individual components work as expected, catches regressions, and documents intended behavior
• D. It replaces the need for integration tests

Answer: (C)

Unit testing concentrates on checking the smallest testable parts of code—individual components or functions—in isolation from the rest of the system. This focus makes it ideal for verifying that each piece behaves as expected, including how it handles typical inputs and edge cases, and for catching regressions when the code changes. In addition, well-written unit tests serve as living documentation of how a component is supposed to be used and what results it should produce. This approach is not about running the entire system in production-like conditions—that would be handled by system or integration testing. It’s also not about optimizing performance; performance testing targets speed and scalability. And it doesn’t replace integration tests, which verify that different parts of the system work together correctly. Instead, unit tests complement those tests by ensuring each part functions correctly on its own, making it easier to diagnose failures when higher-level tests fail.