Which is not a Component testing
-
Check the memory leaks
-
Check the robustness
-
Check the branch coverage
-
Check the decision tables
Component testing focuses on individual software components. Memory leak checking, robustness testing, and branch coverage are all component-level testing activities. Decision table testing is a system-level or acceptance testing technique that examines complex business logic and decision rules, not component behavior.
To answer this question, you need to understand component testing. Component testing is a level of testing that focuses on testing individual components or modules of a software system.
Let's go through each option to understand why it is correct or incorrect:
Option A) Check the memory leaks - This option is a component testing activity. Component testing involves checking for memory leaks in the individual components or modules of a software system.
Option B) Check the robustness - This option is a component testing activity. Component testing involves checking the robustness of individual components or modules.
Option C) Check the branch coverage - This option is a component testing activity. Component testing involves checking the branch coverage of individual components or modules.
Option D) Check the decision tables - This option is not a component testing activity. Decision tables are used in other types of testing, such as functional testing or integration testing, to test the logic and decision-making capabilities of a system.
The correct answer is D. This option is not a component testing activity because decision tables are not specifically associated with component testing.