mirror of
https://github.com/puppeteer/puppeteer
synced 2024-06-14 14:02:48 +00:00
6e484ffbdb
Bumps [glob](https://github.com/isaacs/node-glob) from 8.0.3 to 8.1.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/isaacs/node-glob/blob/main/changelog.md">glob's changelog</a>.</em></p> <blockquote> <h2>8.1</h2> <ul> <li>Add <code>windowsPathsNoEscape</code> option</li> </ul> <h2>8.0</h2> <ul> <li>Only support node v12 and higher</li> <li><code>\</code> is now <strong>only</strong> used as an escape character, and never as a path separator in glob patterns, so that Windows users have a way to match against filenames containing literal glob pattern characters.</li> <li>Glob pattern paths <strong>must</strong> use forward-slashes as path separators, since <code>\</code> is an escape character to match literal glob pattern characters.</li> <li>(8.0.2) <code>cwd</code> and <code>root</code> will always be automatically coerced to use <code>/</code> as path separators on Windows, as they cannot contain glob patterns anyway, and are often supplied by <code>path.resolve()</code> and other methods that will use <code>\</code> path separators by default.</li> </ul> <h2>7.2</h2> <ul> <li>Add fs option to allow passing virtual filesystem</li> </ul> <h2>7.1</h2> <ul> <li>Ignore stat errors that are not <code>ENOENT</code> to work around Windows issues.</li> <li>Support using root and absolute options together</li> <li>Bring back lumpy space princess</li> <li>force 'en' locale in string sorting</li> </ul> <h2>7.0</h2> <ul> <li>Raise error if <code>options.cwd</code> is specified, and not a directory</li> </ul> <h2>6.0</h2> <ul> <li>Remove comment and negation pattern support</li> <li>Ignore patterns are always in <code>dot:true</code> mode</li> </ul> <h2>5.0</h2> <ul> <li>Deprecate comment and negation patterns</li> <li>Fix regression in <code>mark</code> and <code>nodir</code> options from making all cache keys absolute path.</li> <li>Abort if <code>fs.readdir</code> returns an error that's unexpected</li> <li>Don't emit <code>match</code> events for ignored items</li> <li>Treat ENOTSUP like ENOTDIR in readdir</li> </ul> <h2>4.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .. | ||
| assets | ||
| fixtures | ||
| golden-chromium | ||
| golden-firefox | ||
| installation | ||
| src | ||
| .eslintrc.js | ||
| package.json | ||
| README.md | ||
| TestExpectations.json | ||
| TestSuites.json | ||
| tsconfig.json | ||
Puppeteer tests
Unit tests in Puppeteer are written using Mocha as the test runner and Expect as the assertions library.
Test state
We have some common setup that runs before each test and is defined in mocha-utils.js.
You can use the getTestState function to read state. It exposes the following that you can use in your tests. These will be reset/tidied between tests automatically for you:
puppeteer: an instance of the Puppeteer library. This is exactly what you'd get if you ranrequire('puppeteer').puppeteerPath: the path to the root source file for Puppeteer.defaultBrowserOptions: the default options the Puppeteer browser is launched from in test mode, so tests can use them and override if required.server: a dummy test server instance (seepackages/testserverfor more).httpsServer: a dummy test server HTTPS instance (seepackages/testserverfor more).isFirefox: true if running in Firefox.isChrome: true if running Chromium.isHeadless: true if the test is in headless mode.
If your test needs a browser instance, you can use the setupTestBrowserHooks() function which will automatically configure a browser that will be cleaned between each test suite run. You access this via getTestState().
If your test needs a Puppeteer page and context, you can use the setupTestPageAndContextHooks() function which will configure these. You can access page and context from getTestState() once you have done this.
The best place to look is an existing test to see how they use the helpers.
Skipping tests in specific conditions
To skip tests edit the TestExpecations file. See test runner documentation for more details.
Running tests
- To run all tests applicable for your platform:
npm test
- Important: don't forget to first build the code if you're testing local changes:
npm run build && npm test
- To run a specific test, substitute the
itwithit.only:
...
it.only('should work', async function() {
const {server, page} = getTestState();
const response = await page.goto(server.EMPTY_PAGE);
expect(response.ok).toBe(true);
});
- To disable a specific test, substitute the
itwithit.skip:
...
it.skip('should work', async function({server, page}) {
const {server, page} = getTestState();
const response = await page.goto(server.EMPTY_PAGE);
expect(response.ok).toBe(true);
});
- To run Chrome headful tests:
npm run test:chrome:headful
- To run tests with custom browser executable:
BINARY=<path-to-executable> npm run test:chrome:headless # Or npm run test:firefox