Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
TypeScript automationchromechromiume2e-testingelectronend-to-end-testingfirefoxjavascriptplaywrighttesttest-automationtestingtesting-toolswebwebkit
docs: move one image to src/images (#36857)
Simon Knott31d5434b081b
diff --git a/docs/src/browsers.md b/docs/src/browsers.mdindex c2c8449171..aafa274b5b 100644--- a/docs/src/browsers.md+++ b/docs/src/browsers.md@@ -232,7 +232,7 @@ Running 1 test using 1 workerWith the VS Code extension you can run your tests on different browsers by checking the checkbox next to the browser name in the Playwright sidebar. These names are defined in your Playwright config file under the projects section. The default config when installing Playwright gives you 3 projects, Chromium, Firefox and WebKit. The first project is selected by default.-+To run tests on multiple projects(browsers), select each project by checking the checkboxes next to the project name.diff --git a/docs/src/images/vscode-projects-section.png b/docs/src/images/vscode-projects-section.pngnew file mode 100644index 0000000000..d304dd04f9Binary files /dev/null and b/docs/src/images/vscode-projects-section.png differdiff --git a/utils/doclint/cli.js b/utils/doclint/cli.jsindex a388d860d0..a694cd0749 100755--- a/utils/doclint/cli.js+++ b/utils/doclint/cli.js@@ -247,6 +247,8 @@ async function run() {const badLinks = [];for (const { filePath, linkTarget, name } of mdLinks) {+ if (linkTarget.startsWith(path.join(documentationRoot, 'images')))+ continue;if (!mdSections.has(linkTarget))badLinks.push(`${path.relative(PROJECT_DIR, filePath)} references to '${linkTarget}' as '${name}' which does not exist.`);}