-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jestPuppeteer.debug support in Jest-circus #255
Comments
Hello @brbrr, yeah |
make sense. What would you recommend as an alternative? I wonder if we can use some sort of |
Hello yes maybe it would be a good solution but no very user-friendly. |
Have you tried adding freaky timeout as test argument?(I'm not using custom environment, just add jestPuppeteer.debug() to each test while test development) jest.retryTimes(3)
describe('Test', () => {
test('Test_1', async () => {
await loginPage.login()
await jestPuppeteer.debug() //paused in browser, and after resuming in browser stays paused in test runner
await loginPageAssert.isLoggedIn()
}, 999999) //timeout
}) |
This question is asked all over the place. The timeout https://github.com/smooth-code/jest-puppeteer/blob/master/packages/jest-environment-puppeteer/src/PuppeteerEnvironment.js#L42 is maybe ignored due to the same reason as jestjs/jest#9359. You can use |
💬 Questions and Help
I wonder if there any plans to support jest-circus. While
jest-circus
works kinda fine out of the box, I noticed thatjestPuppeteer.debug()
does not really work as expected.I have this
CustomEnvironemnt
class that should stop the execution on test failure:It does trigger the chrome's debugger, but unfortunately, after resuming the debugger - browser just closes itself.
The text was updated successfully, but these errors were encountered: