System and Functional Testing: which statement is true?

• A. Does not include security testing of databases
• B. Is done in an ad hoc fashion as staff are available
• C. Addresses cultural impacts of new processes
• D. Includes multiple subsystems and phases of testing

Answer: (D)

System and functional testing are about validating the entire, integrated system across all interdependent parts and across different testing activities. Because the product spans multiple modules and interfaces, tests must cover end-to-end workflows that cross component boundaries and verify that each function works as required while the modules work together. This approach naturally includes multiple phases of testing, such as functional validation of individual features, integration tests to check interactions between subsystems, regression tests to ensure changes don’t break existing behavior, and nonfunctional tests like performance and security considerations.

The idea that security testing is excluded isn’t accurate for system testing, since security considerations are typically part of the test plan and may be conducted within system or dedicated security testing. System testing also isn’t conducted in an ad hoc fashion; it’s planned and structured to ensure the whole system behaves correctly in real-world scenarios. Cultural or organizational impacts are outside the testing scope, as they relate more to change management than to validating the software’s functionality and integration.

For example in a hospital information system, system testing would verify end-to-end patient care processes across modules—admission, orders, lab results, medication administration, and billing—ensuring data flows correctly, access controls are enforced, and the system performs under expected conditions. This illustrates why the statement describing system testing as including multiple subsystems and phases is the true one.