A mobile device has some peripherals attached to it, if your application uses a peripheral of them to operate, what should you do regarding this…

A comprehensive test strategy for an application dependent on a peripheral must validate two key scenarios. First, testing with the peripheral ensures the application correctly utilizes the hardware for its intended features (interoperability). Second, testing without the peripheral is crucial for robustness testing. This verifies that the application handles the absence of the hardware gracefully, for instance, by displaying an informative message or disabling the relevant feature, rather than crashing or behaving unpredictably. This approach covers both positive and negative test cases for the dependency.

A. Testing the peripheral in isolation is hardware component testing, not the responsibility of the application tester, whose focus is on the integrated system.

B. This approach is incomplete. It only covers the "happy path" and fails to test the application's robustness and error handling when the peripheral is unavailable.

D. This suggests an unstructured, incidental approach. Effective testing requires a deliberate strategy to cover specific conditions, not assuming they will be tested "anyway."

1. ISTQB® Certified Tester Foundation Level Mobile Application Testing Syllabus 2019: Section 3.2.3, "Interoperability Testing," states that testing should focus on the "interaction with peripherals (e.g., headsets, chargers, external keyboards...)." This supports the requirement to test with the peripheral.

2. ISTQB® Certified Tester Advanced Level Technical Test Analyst Syllabus Version 4.0 (2021): Section 4.3.2, "Robustness," defines robustness testing as determining "the degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions." The absence of a required peripheral is a stressful condition that must be tested, supporting the need to test without it.

3. Koomen, T., van der Aalst, L., Broekman, B., & Vroon, M. (2006). TMap Next: For result-driven testing. UTN Publishers. (A foundational text in software testing methodology often referenced in academic settings). Chapter 14, "Specification techniques," discusses cause-effect graphing and decision table testing, which encourage testing all combinations of conditions. In this context, the presence or absence of the peripheral are two distinct causes whose effects on the application must be explicitly tested.