Automation Testing Automation Functional Testing 5

Question 1

What is the recommended scope of a single well-designed functional automated test?

Accepted Answer

Verify one specific behavior or scenario

Answer

Test the entire application end to end

Answer

Only print logs

Answer

Validate code style

Question 2

Which is a benefit of integrating functional automation into a CI/CD pipeline?

Accepted Answer

Fast feedback on regressions with each change

Answer

Tests run only manually

Answer

Slower releases

Answer

No need for assertions

Question 3

What does 'test coverage' measure in functional automation?

Accepted Answer

The amount of code or requirements exercised by tests

Answer

The size of the browser window

Answer

The number of developers

Answer

The screen resolution

Question 4

Why should automated tests avoid depending on execution order?

Accepted Answer

Order dependence makes tests fragile and hard to parallelize

Answer

It improves speed

Answer

It increases coverage

Answer

It removes flakiness automatically

Question 5

What is a common use of mocking or stubbing in functional automation?

Accepted Answer

To replace unstable external dependencies with controlled responses

Answer

To delete the test code

Answer

To increase real network traffic

Answer

To skip all assertions

Question 6

Which metric best reflects the maintainability cost of a test suite?

Accepted Answer

Frequency of tests needing updates due to minor UI changes

Answer

Number of monitors used

Answer

Color of the IDE theme

Answer

Length of variable names only

Question 7

What is the main goal of regression testing through automation?

Accepted Answer

To confirm existing features still work after changes

Answer

To design new features

Answer

To measure server temperature

Answer

To write documentation