Playwright and Testing Patterns Quiz

What is the purpose of using storage-state in Playwright tests?

• To save cookies and local storage once and skip UI login in all tests

• To manage environment variables

• To configure the test runner

• To define test dependencies

What is the role of .env files and dotenv in a project?

• To keep configuration and secrets outside the code

• To define test cases

• To manage test reports

• To handle network requests

What is the difference between global setup and normal tests in Playwright?

• Global setup runs once before the suite; ideal for calling storage-state util

• Global setup runs after each test

• Global setup is used for defining test cases

• Global setup is used for generating reports

What does the Playwright HTML reporter provide?

• Default single-run view with traces and screenshots when enabled

• Integration with CI/CD pipelines

• Network request handling

• Environment variable management

What is included in the playwright.config.js file?

• Reporter, projects, use block, timeouts, retries

• Test cases

• Environment variables

• Network configurations

What is the project dependency pattern in Playwright?

• The 'setup' project runs first, and others depend on it

• All projects run independently

• Projects are defined in the .env file

• Projects are managed by the test runner

What is the purpose of a custom runner in Playwright?

• To extend the base test to inject fixtures

• To manage environment variables

• To handle network requests

• To generate test reports

What are the benefits of using the Allure reporter over the built-in HTML reporter?

• Allure offers history, widgets, and flaky tracking

• Allure is faster

• Allure integrates with more CI/CD tools

• Allure is easier to configure

What is a circular-import pitfall and how can it be fixed?

• Load config first and avoid mutual imports

• Use a different test runner

• Define imports in the .env file

• Use a custom reporter

How can network mocking be toggled in Playwright?

• Via page.route toggled by env.MOCK

• Using a custom test runner

• By defining it in the .env file

• Through the test report configuration