When to automate vs manual test in Testing Fundamentals - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When is automation testing preferred over manual testing?

Choose the best scenario where automation testing is more suitable than manual testing.

A Testing a feature that requires repetitive execution with stable requirements.

B Testing a new feature with frequently changing requirements.

C Exploratory testing to find unexpected bugs.

D Usability testing that requires human judgment.

💡 Hint

Think about when repeating the same steps many times is needed.

Automation is best for repetitive tests with stable requirements because it saves time and reduces human error. Manual testing is better for exploratory or usability tests where human insight is needed.

🧠 Conceptual

intermediate

Why might manual testing be chosen over automation?

Identify the reason manual testing is preferred in some cases.

A When tests need to be run thousands of times quickly.

B When the test is fully scripted and stable.

C When the test requires human intuition and visual feedback.

D When the test is part of a continuous integration pipeline.

💡 Hint

Consider tests that need human feelings or opinions.

Manual testing is preferred when human intuition, judgment, or visual feedback is necessary, such as in usability or exploratory testing.

❓ Predict Output

advanced

What is the output of this test automation decision code?

Given the following Python code that decides whether to automate or manually test a feature, what will be printed?

Testing Fundamentals

def decide_test_type(repetitive: bool, stable_requirements: bool, needs_human_judgment: bool) -> str:
    if repetitive and stable_requirements and not needs_human_judgment:
        return "Automate"
    elif needs_human_judgment:
        return "Manual"
    else:
        return "Manual"

print(decide_test_type(repetitive=True, stable_requirements=False, needs_human_judgment=False))

A Automate

B Manual

C SyntaxError

D TypeError

💡 Hint

Check the conditions carefully and see which branch matches the input.

The function returns "Automate" only if repetitive and stable_requirements are True and needs_human_judgment is False. Here, stable_requirements is False, so it returns "Manual".

❓ assertion

advanced

Which assertion correctly verifies automation suitability?

You have a function should_automate(repetitive, stable_requirements, needs_human_judgment) that returns True if automation is suitable. Which assertion correctly tests that automation is chosen for repetitive and stable tests without human judgment?

Testing Fundamentals

def should_automate(repetitive, stable_requirements, needs_human_judgment):
    return repetitive and stable_requirements and not needs_human_judgment

A assert should_automate(True, True, False) == True

B assert should_automate(True, False, False) == True

C assert should_automate(False, True, False) == True

D assert should_automate(True, True, True) == True

💡 Hint

Check when the function returns True based on the logic.

The function returns True only if repetitive and stable_requirements are True and needs_human_judgment is False. Only option A matches this.

❓ framework

expert

Which test case is best suited for automation in a CI/CD pipeline?

In a continuous integration/continuous deployment (CI/CD) pipeline, which test case below is best suited for automation?

A A test that requires manual approval from a product owner before proceeding.

B A test that requires a tester to evaluate the look and feel of a new UI design.

C A test that involves exploratory steps to find new bugs in a new feature.

D A test that checks if the login page loads correctly every time code is pushed.

💡 Hint

Think about tests that can run automatically without human input in CI/CD.

Tests that verify stable, repeatable functionality like page loading are ideal for automation in CI/CD pipelines. Manual or exploratory tests are not suitable for automation in this context.

Practice

1. Which type of testing is best suited for repetitive tasks that rarely change?

easy

A. Manual testing

B. Automated testing

C. Exploratory testing

D. Ad-hoc testing

Solution

1. Step 1: Understand the nature of repetitive tasks

   Repetitive tasks are those that happen often and have stable expected results.

2. Step 2: Match testing type to task nature

   Automated testing is ideal for repetitive and stable tasks because it saves time and reduces human error.

3. Final Answer:

   Automated testing -> Option B

4. Quick Check:

   Repetitive tasks = Automated testing [OK]

Hint: Automate stable, repetitive tests to save time [OK]

Common Mistakes:

• Choosing manual testing for repetitive tasks wastes time
• Confusing exploratory testing with repetitive testing
• Thinking ad-hoc testing fits repetitive tasks

2. Which of the following is the correct reason to choose manual testing over automation?

easy

A. When tests require human judgment and intuition

B. When tests are simple and can be scripted easily

C. When tests need to run overnight without interruption

D. When tests are repetitive and stable

Solution

1. Step 1: Identify when human insight is needed

   Manual testing is best when tests require human judgment, such as usability or visual checks.

2. Step 2: Compare options to manual testing needs

   When tests require human judgment and intuition matches the need for human intuition, unlike options A, B, and C which favor automation.

3. Final Answer:

   When tests require human judgment and intuition -> Option A

4. Quick Check:

   Human insight = Manual testing [OK]

Hint: Manual testing fits tasks needing human judgment [OK]

Common Mistakes:

• Choosing manual for repetitive stable tests
• Confusing automation needs with manual testing
• Ignoring the role of human intuition

3. Consider this scenario: A test suite runs 100 tests daily. 80 tests are stable and repetitive, 20 are new features needing exploration. Which approach is best?

medium

A. Automate all 100 tests

B. Manually test all 100 tests

C. Automate the 80 stable tests and manually test the 20 new features

D. Manually test the 80 stable tests and automate the 20 new features

Solution

1. Step 1: Analyze test types and their nature

   80 tests are stable and repetitive, suitable for automation; 20 are new and exploratory, better for manual testing.

2. Step 2: Match testing approach to test types

   Automate stable tests to save time; manually test new features for human insight.

3. Final Answer:

   Automate the 80 stable tests and manually test the 20 new features -> Option C

4. Quick Check:

   Stable = automate, new = manual [OK]

Hint: Automate stable tests, manual for new features [OK]

Common Mistakes:

• Automating new exploratory tests that change often
• Manually testing all tests wastes time
• Ignoring test stability when choosing method

4. A tester wrote automated scripts for a feature still under frequent change. What is the main problem with this approach?

medium

A. Scripts will require constant updates, wasting effort

B. Automated tests run faster

C. Manual testing is slower

D. Automation tools cannot test new features

Solution

1. Step 1: Understand impact of frequent changes on automation

   When features change often, automated scripts break and need frequent fixes.

2. Step 2: Identify the problem caused by frequent script updates

   Constant updates waste time and reduce automation benefits.

3. Final Answer:

   Scripts will require constant updates, wasting effort -> Option A

4. Quick Check:

   Frequent changes = costly automation maintenance [OK]

Hint: Avoid automating unstable features to save maintenance [OK]

Common Mistakes:

• Thinking automation tools can't test new features
• Confusing speed with suitability
• Ignoring maintenance cost of automation

5. You manage testing for a complex app with frequent UI changes and critical backend logic. How should you balance automation and manual testing?

hard

A. Automate UI tests and manually test backend logic

B. Automate both UI and backend tests fully

C. Manually test both UI and backend tests fully

D. Manually test UI and automate backend logic tests

Solution

1. Step 1: Analyze UI and backend characteristics

   UI changes frequently, making automation brittle; backend logic is stable and critical, suitable for automation.

2. Step 2: Choose testing method per component

   Manual testing fits UI due to frequent changes and human insight; automate backend logic for reliability and speed.

3. Final Answer:

   Manually test UI and automate backend logic tests -> Option D

4. Quick Check:

   UI frequent changes = manual, backend stable = automate [OK]

Hint: Automate stable backend; manual test changing UI [OK]

Common Mistakes:

• Automating frequently changing UI causing flaky tests
• Manually testing stable backend wasting time
• Ignoring test stability and criticality