When should test cases be automated?

• A. If they are low risk and unlikely to change
• B. If they require extensive documentation
• C. If they require manual execution every time
• D. If they have multiple dependencies

Answer: (A)

Test cases should be automated when they are low risk and unlikely to change because automation provides efficiency and repeatability for these scenarios. Low-risk tests typically mean that the tests are stable and well-understood, allowing automation to be implemented without the worry of frequent updates or modifications. This stability makes it cost-effective to automate since the initial investment in scripting and setting up the tests will yield a high return through repeated execution without significant maintenance overhead.

On the other hand, test cases that require extensive documentation may suggest complexity or frequent changes, making them less suitable for automation until they are fully stabilized. Test cases that necessitate manual execution every time could indicate they involve exploratory or unfamiliar areas where human judgement is essential, thus not benefiting from automation. Additionally, cases with multiple dependencies can complicate automation due to the need for a stable environment, making it challenging to set up and execute automated tests reliably.

Overall, choosing to automate low-risk, stable test cases aligns with best practices in software testing, maximizing efficiency and resource management.