Playwright With Typescript Interview Questions
1. What is Playwright?
Playwright is an open-source end-to-end testing framework created by Microsoft for web applications. It allows reliable automation of Chromium, Firefox, and WebKit browsers, making it possible to test modern features across platforms.
2. Which browsers does Playwright support?
Playwright with TypeScript interview questions often highlight that Playwright supports Chromium-based browsers such as Chrome and Edge, Firefox, and WebKit (which powers Safari). This wide support ensures cross-browser testing without additional setup
3. Does Playwright support TypeScript?
Yes, Playwright has built-in TypeScript definitions which provide type safety and autocompletion. This makes it easier to catch mistakes at compile time and improves developer productivity.
4. How is Playwright different from Selenium?
Playwright is faster, supports auto-waiting for elements, and works better with single-page applications. Unlike Selenium, it can handle multiple browser contexts and modern web features with less setup.
5. Can Playwright run tests in parallel?
Yes, Playwright supports parallel execution of tests by default at the file level. This allows faster execution times by distributing tests across multiple workers.
6. What programming languages are supported by Playwright?
Playwright provides official support for JavaScript, TypeScript, Python, Java, and .NET. This flexibility makes it accessible for teams using different technology stacks.
7. What is the Playwright test runner?
The Playwright test runner is a built-in testing framework that manages test execution. It supports fixtures, retries, parallelism, reporters, and advanced debugging tools out of the box.
8. Can Playwright run tests in headless and headed modes?
Yes, Playwright can run tests in headless mode by default or headed mode for debugging. Headless is faster, while headed is useful for visual verification — and this is one of the common points discussed in Playwright with TypeScript interview questions
9. What is the default execution mode in Playwright?
Playwright runs in headless mode by default. This reduces overhead and improves test speed, but you can switch to headed mode for debugging.
10. How does Playwright handle asynchronous operations?
Playwright APIs return promises and must be used with async and await. This ensures test steps execute in the correct order and handle asynchronous page interactions.
11. What is a locator in Playwright?
A locator is an object that finds and interacts with elements on the page. It is lazy, meaning it waits until an element is ready before acting, reducing flakiness in tests.
12. What is the difference between locator and element handle?
A locator retries automatically until the element is actionable, while an element handle represents a fixed snapshot of a DOM node. Locators are generally preferred because they reduce timing issues.
13. What is auto-waiting in Playwright?
Auto-waiting means Playwright waits automatically for elements to be visible, enabled, and stable before performing actions. This eliminates the need for manual waits and reduces flaky tests.
14. How can you perform a click action in Playwright?
You locate the element and then perform a click on it. Playwright ensures the element is interactable before performing the action.
15. How can you type text into an input field?
By locating the input field and filling or typing text into it. Playwright ensures the element is visible and enabled before sending keystrokes.
16. How can you select an option from a dropdown?
You can select options by specifying their value, label, or index. Playwright will interact with the underlying select element directly.
17. How can you perform a hover action?
By hovering the mouse over a specific element. This is useful for triggering tooltips, dropdown menus, or other hover-based interactions.
18. How does Playwright handle keyboard events?
Playwright provides methods to simulate key presses, key combinations, and typing. This makes it possible to test keyboard shortcuts and form inputs.
19. How can you perform drag-and-drop in Playwright?
By dragging one element and dropping it onto another target element. Playwright simulates the complete user interaction including mouse down, move, and up events.
20. How does Playwright handle browser dialogs like alerts?
It listens for dialog events and allows you to accept, dismiss, or provide input. This is necessary for handling JavaScript alerts, confirms, and prompts during tests.
21. What is Playwright Test’s assertion library used for?
It is used to verify conditions like element visibility, text content, page title, and attributes. Assertions help validate expected outcomes and ensure test reliability.
22. How do you assert a page title in Playwright?
You use the built-in assertion for checking page titles. It ensures that the current page matches the expected title string or pattern.
23. How do you assert element text in Playwright?
You check the locator’s text content against an expected value. This validates that the application displayed the correct output.
24. How can you wait for navigation to complete?
You use Playwright’s built-in wait methods to detect navigation events. This ensures the page has fully loaded before proceeding to the next step.
25. How can you wait for a network response?
You wait for a specific response to a network request. This is useful for validating backend API calls triggered by user actions.
26. How do you group tests in Playwright?
You group them into describe blocks to organize related scenarios. This improves readability and makes test suites easier to manage.
27. How do you run only a single test?
By marking it with the only modifier. This allows focusing on one test case while debugging or developing.
28. How do you skip a test in Playwright?
By marking it with the skip modifier. This prevents the test from running without deleting it from the suite.
29. How can you parameterize tests?
By running the same test with multiple sets of input data. This helps reduce duplication and improves test coverage.
30. How can you share setup across multiple tests?
By using fixtures or hooks like beforeAll and afterAll. These provide reusable setup and cleanup logic for test suites.
31. What is a browser context in Playwright?
A browser context is an isolated environment in a single browser instance. Each context behaves like a separate incognito window with independent cookies and storage.
32. How do you test multiple users simultaneously?
By creating multiple browser contexts in the same test. Each context can represent a different user session.
33. How can you intercept network requests in Playwright?
By routing specific requests and choosing to modify, block, or continue them. This is useful for stubbing or testing error handling.
34. How can you mock API responses?
By intercepting requests and fulfilling them with custom responses. This allows testing scenarios without depending on real backend services.
35. How can you capture screenshots in Playwright?
By saving the state of a page or element as an image. Screenshots are commonly used for visual regression testing and debugging.
36. Does Playwright support video recording of tests?
Yes, Playwright can record test execution as a video. This feature helps analyze failures by watching what happened during a test.
37. What is Playwright trace viewer?
It is a debugging tool that shows detailed traces of test execution. It includes steps, logs, screenshots, and timings to help understand test behavior.
38. How do you handle multiple tabs in Playwright?
By waiting for new page events and switching to them. This allows testing workflows that open links in new tabs or windows.
39. How can you test iframes in Playwright?
By identifying the frame and switching context to interact with elements inside it. This is necessary when applications embed content in iframes.
40. Can Playwright emulate mobile devices?
Yes, Playwright can emulate devices like iPhones and Pixels. It applies viewport sizes, user agents, and touch support to simulate real devices.
41. What is playwright.config.ts used for?
It is a configuration file that defines global settings like browsers, base URL, timeouts, and retries. This centralizes configuration across all tests.
42. How can you set a base URL in Playwright?
By specifying it in the configuration file under the use option. This allows you to write tests with relative paths instead of full URLs.
43. How can you configure retries for flaky tests?
By setting the retries option in the configuration file. This makes Playwright re-run failed tests automatically a given number of times.
44. What reporters are supported in Playwright?
Playwright supports built-in reporters such as list, dot, line, JSON, and HTML. It also supports writing custom reporters for specific needs.
45. How do you generate an HTML test report?
By enabling the HTML reporter in the configuration or through command-line options. The generated report provides a user-friendly test summary.
46. Why use TypeScript with Playwright?
TypeScript provides static typing and compile-time error detection. It improves test reliability by catching mistakes early and providing better IntelliSense.
47. How do you define types for test data in Playwright?
You use TypeScript interfaces or type aliases to define structured data. This ensures consistent usage of test data across tests.
48. How can you organize reusable functions in Playwright with TypeScript?
By placing them in utility or helper files and importing them into tests. This reduces duplication and keeps test files clean.
49. What is the recommended project structure for Playwright with TypeScript?
A common structure separates tests, fixtures, utilities, and configuration into folders. This improves maintainability and scalability of test projects.
50. What are some best practices when writing Playwright tests with TypeScript?
Use locators instead of raw selectors, keep tests atomic and independent, reuse fixtures, save authentication state, and organize code into reusable modules. These practices reduce flakiness and improve readability.
