Hello @sidharth shukla 

Why is mocking useful in API testing?

B. To simulate API behavior when the actual API is unavailable

Mocking is crucial in API testing because it allows testers to simulate API behavior without relying on the actual API. This is especially useful when the API is under development, unavailable, or expensive to use. It ensures that testing can proceed independently of external factors.

What is the difference between a stub and a spy in API testing?

A. A stub mimics behavior, while a spy tracks API call details

A stub is used to mimic specific behavior of an API by providing predefined responses, often for testing specific scenarios. A spy, on the other hand, records details about the API calls such as the number of invocations, arguments passed, and sometimes response details. Spies are useful for tracking interactions without changing the API’s behavior.

Which of the following is NOT a tool mentioned for API mocking?

D. Playwright

While Mockito, WireMock, and Postman are commonly used for API mocking, Playwright is primarily an end-to-end testing tool with support for web automation and does not focus solely on API mocking.

What does Playwright’s built-in mocking feature allow you to do?

B. Intercept, modify, and block network requests during test execution

Playwright’s built-in network interception feature lets you capture, modify, or block network requests during test execution, which helps in controlling the flow of tests that depend on external APIs and services.

What is a key benefit of using Playwright’s mocking feature in API testing?

A. It replaces real API calls with predefined responses, ensuring faster and more reliable tests

Playwright’s mocking feature helps you replace actual API calls with predefined responses, speeding up tests and ensuring reliability even when external services are unstable or unavailable.

Thanks,

Ramanan