You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
We need a way to wrap the page that is not based on global variables (patch playwright?), but also to associate it with the specific running test of mocha.
The text was updated successfully, but these errors were encountered:
This is a lot of code for something you'd really want to be:
before(asyncfunction(): Promise<void>{browser=awaitbrowserType.launch({headless: process.argv.indexOf('--headless')!==-1});// yes this is ugly I know but for the sake of the example.page=awaitattach(await(awaitbrowser.newContext()).newPage());awaitpage.setViewportSize({ width, height });});
The user has A LOT to fill in when it's not set up by hooking into the test runner 🤷🏻♂️
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given the following example:
https://github.com/xtermjs/xterm.js/blob/master/test/api/MouseTracking.api.ts#L213-L219
The test runner is mocha
The browser and page are local variables in the module scope, and not global.
The before call is nested inside the
describe
The page is created once, and re-used in all of the tests.
We need a way to wrap the page that is not based on global variables (patch playwright?), but also to associate it with the specific running test of mocha.
The text was updated successfully, but these errors were encountered: