What activity should not be included in Factory Acceptance Test (FAT)?

What activity should not be included in Factory Acceptance Test (FAT)?

• A. Accuracy of documentation
• B. Testing for electromagnetic compatibility
• C. Hardware fault creation
• D. Interface testing

Answer: (C)

In the context of a Factory Acceptance Test (FAT), the activity that should not be included is hardware fault creation. FAT is designed to ensure that the system, as built, meets its specifications and is functioning correctly before it is shipped to the customer or deployed in its operational environment. The focus of FAT is primarily on validating the performance of the functional aspects of the system, ensuring compliance with design specifications, and verifying that the system operates as intended. Hardware fault creation is not an appropriate activity for FAT because the goal of this test phase is to confirm that the hardware is functioning correctly and is free from faults. Introducing faults deliberately during FAT would undermine this objective and might lead to unnecessary complications or delays in the testing process. Instead, fault creation would typically be part of a different testing phase, possibly during reliability or stress testing, where the resilience of the system to faults is assessed under controlled conditions. Other activities, such as verifying the accuracy of documentation, testing for electromagnetic compatibility, and conducting interface testing, align well with the goals of FAT, as they focus on ensuring completeness, compliance, and proper operation of the system.

In the context of a Factory Acceptance Test (FAT), the activity that should not be included is hardware fault creation. FAT is designed to ensure that the system, as built, meets its specifications and is functioning correctly before it is shipped to the customer or deployed in its operational environment. The focus of FAT is primarily on validating the performance of the functional aspects of the system, ensuring compliance with design specifications, and verifying that the system operates as intended.

Hardware fault creation is not an appropriate activity for FAT because the goal of this test phase is to confirm that the hardware is functioning correctly and is free from faults. Introducing faults deliberately during FAT would undermine this objective and might lead to unnecessary complications or delays in the testing process. Instead, fault creation would typically be part of a different testing phase, possibly during reliability or stress testing, where the resilience of the system to faults is assessed under controlled conditions.

Other activities, such as verifying the accuracy of documentation, testing for electromagnetic compatibility, and conducting interface testing, align well with the goals of FAT, as they focus on ensuring completeness, compliance, and proper operation of the system.