Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
eslint-plugin-playwright
Advanced tools
eslint-plugin-playwright is an ESLint plugin that provides linting rules specific to Playwright, a Node.js library for browser automation. This plugin helps ensure best practices and code quality when writing tests with Playwright.
No Page Pause
This rule disallows the use of `page.pause()` in your Playwright tests to prevent unintended pauses during test execution.
module.exports = {
plugins: ['playwright'],
rules: {
'playwright/no-page-pause': 'error'
}
};
No Element Handle
This rule discourages the use of `elementHandle` in favor of using locators, which are more robust and easier to work with.
module.exports = {
plugins: ['playwright'],
rules: {
'playwright/no-element-handle': 'error'
}
};
No Wait For Timeout
This rule prevents the use of `page.waitForTimeout()` to avoid flaky tests caused by arbitrary wait times.
module.exports = {
plugins: ['playwright'],
rules: {
'playwright/no-wait-for-timeout': 'error'
}
};
eslint-plugin-jest provides linting rules specific to Jest, a popular JavaScript testing framework. It helps enforce best practices and code quality in Jest tests. While eslint-plugin-playwright focuses on Playwright-specific rules, eslint-plugin-jest is tailored for Jest.
eslint-plugin-cypress offers linting rules for Cypress, another end-to-end testing framework. It ensures best practices and code quality in Cypress tests. Similar to eslint-plugin-playwright, but for Cypress instead of Playwright.
eslint-plugin-testing-library provides linting rules for Testing Library, a set of utilities for testing UI components. It helps ensure best practices and code quality when using Testing Library. While eslint-plugin-playwright is for Playwright, this plugin is for Testing Library.
ESLint plugin for Playwright.
npm
npm install -D eslint-plugin-playwright
Yarn
yarn add -D eslint-plugin-playwright
pnpm
pnpm add -D eslint-plugin-playwright
The recommended setup is to use the files
field to target only Playwright test
files. In the examples below, this is done by targeting files in the tests
directory and only applying the Playwright rules to those files. In your
project, you may need to change the files
field to match your Playwright test
file patterns.
Flat config (eslint.config.js)
import playwright from 'eslint-plugin-playwright'
export default [
{
...playwright.configs['flat/recommended'],
files: ['tests/**'],
rules: {
...playwright.configs['flat/recommended'].rules,
// Customize Playwright rules
// ...
},
},
]
Legacy config (.eslintrc)
{
"overrides": [
{
"files": "tests/**",
"extends": "plugin:playwright/recommended"
}
]
}
If you import Playwright globals (e.g. test
, expect
) with a custom name, you
can configure this plugin to be aware of these additional names.
{
"settings": {
"playwright": {
"globalAliases": {
"test": ["myTest"],
"expect": ["myExpect"]
}
}
}
}
You can customize the error messages for rules using the
settings.playwright.messages
property. This is useful if you would like to
increase the verbosity of error messages or provide additional context.
Only the message ids you define in this setting will be overridden, so any other messages will use the default message defined by the plugin.
{
"settings": {
"playwright": {
"messages": {
"conditionalExpect": "Avoid conditional expects as they can lead to false positives"
}
}
}
}
✅ Set in the recommended
configuration
🔧 Automatically fixable by the --fix
CLI option
💡 Manually fixable by
editor suggestions
Rule | Description | ✅ | 🔧 | 💡 |
---|---|---|---|---|
expect-expect | Enforce assertion to be made in a test body | ✅ | ||
max-expects | Enforces a maximum number assertion calls in a test body | |||
max-nested-describe | Enforces a maximum depth to nested describe calls | ✅ | ||
missing-playwright-await | Enforce Playwright APIs to be awaited | ✅ | 🔧 | |
no-commented-out-tests | Disallow commented out tests | |||
no-conditional-expect | Disallow calling expect conditionally | ✅ | ||
no-conditional-in-test | Disallow conditional logic in tests | ✅ | ||
no-duplicate-hooks | Disallow duplicate setup and teardown hooks | |||
no-element-handle | Disallow usage of element handles | ✅ | 💡 | |
no-eval | Disallow usage of page.$eval() and page.$$eval() | ✅ | ||
no-focused-test | Disallow usage of .only annotation | ✅ | 💡 | |
no-force-option | Disallow usage of the { force: true } option | ✅ | ||
no-get-by-title | Disallow using getByTitle() | 🔧 | ||
no-hooks | Disallow setup and teardown hooks | |||
no-nested-step | Disallow nested test.step() methods | ✅ | ||
no-networkidle | Disallow usage of the networkidle option | ✅ | ||
no-nth-methods | Disallow usage of first() , last() , and nth() methods | |||
no-page-pause | Disallow using page.pause() | ✅ | ||
no-raw-locators | Disallow using raw locators | |||
no-restricted-matchers | Disallow specific matchers & modifiers | |||
no-skipped-test | Disallow usage of the .skip annotation | ✅ | 💡 | |
no-standalone-expect | Disallow using expect outside of test blocks | ✅ | ||
no-unsafe-references | Prevent unsafe variable references in page.evaluate() | ✅ | 🔧 | |
no-useless-await | Disallow unnecessary await s for Playwright methods | ✅ | 🔧 | |
no-useless-not | Disallow usage of not matchers when a specific matcher exists | ✅ | 🔧 | |
no-wait-for-selector | Disallow usage of page.waitForSelector() | ✅ | 💡 | |
no-wait-for-timeout | Disallow usage of page.waitForTimeout() | ✅ | 💡 | |
prefer-comparison-matcher | Suggest using the built-in comparison matchers | 🔧 | ||
prefer-equality-matcher | Suggest using the built-in equality matchers | 💡 | ||
prefer-hooks-in-order | Prefer having hooks in a consistent order | |||
prefer-hooks-on-top | Suggest having hooks before any test cases | |||
prefer-lowercase-title | Enforce lowercase test names | 🔧 | ||
prefer-native-locators | Suggest built-in locators over page.locator() | 🔧 | ||
prefer-locator | Suggest locators over page methods | |||
prefer-strict-equal | Suggest using toStrictEqual() | 💡 | ||
prefer-to-be | Suggest using toBe() | 🔧 | ||
prefer-to-contain | Suggest using toContain() | 🔧 | ||
prefer-to-have-count | Suggest using toHaveCount() | 🔧 | ||
prefer-to-have-length | Suggest using toHaveLength() | 🔧 | ||
prefer-web-first-assertions | Suggest using web first assertions | ✅ | 🔧 | |
require-hook | Require setup and teardown code to be within a hook | |||
require-soft-assertions | Require assertions to use expect.soft() | 🔧 | ||
require-to-throw-message | Require a message for toThrow() | |||
require-top-level-describe | Require test cases and hooks to be inside a test.describe block | |||
valid-describe-callback | Enforce valid describe() callback | ✅ | ||
valid-expect-in-promise | Require promises that have expectations in their chain to be valid | ✅ | ||
valid-expect | Enforce valid expect() usage | ✅ | ||
valid-title | Enforce valid titles | ✅ | 🔧 |
FAQs
ESLint plugin for Playwright testing.
The npm package eslint-plugin-playwright receives a total of 1,179,014 weekly downloads. As such, eslint-plugin-playwright popularity was classified as popular.
We found that eslint-plugin-playwright demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.