Automation Testing Automation Functional Testing 3

Question 1

What is the main benefit of running functional automation tests in parallel?

Accepted Answer

Reduced total execution time

Answer

Guaranteed zero flakiness

Answer

Smaller test code

Answer

Higher network latency

Question 2

Which practice best supports maintainable automated test code?

Accepted Answer

Reusable helper methods and clear naming

Answer

Hardcoding values everywhere

Answer

One giant test method

Answer

Avoiding all comments

Question 3

What is a smoke test in an automated functional context?

Accepted Answer

A quick check of critical core functionality

Answer

An exhaustive test of every feature

Answer

A performance stress test

Answer

A security penetration test

Question 4

When should a functional automated test ideally fail fast?

Accepted Answer

As soon as a critical precondition is not met

Answer

Only at the very end

Answer

Never, to gather all data

Answer

Only on the third retry

Question 5

What is the role of a test runner in an automation framework?

Accepted Answer

Discovering, executing, and reporting tests

Answer

Designing UI mockups

Answer

Writing production code

Answer

Managing customer support

Question 6

Which is a strong indicator that a UI test should be moved to the API level instead?

Accepted Answer

It validates backend logic not visual layout

Answer

It uses a unique ID locator

Answer

It runs in under one second

Answer

It has a clear assertion

Question 7

What does idempotency mean for an automated test setup step?

Accepted Answer

Running it multiple times yields the same state

Answer

It can only run once

Answer

It must use random data

Answer

It disables cleanup