jestPuppeteer.debug support in Jest-circus

💬 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 that jestPuppeteer.debug() does not really work as expected.

I have this CustomEnvironemnt class that should stop the execution on test failure:

const PuppeteerEnvironment = require( 'jest-environment-puppeteer' );

class CustomEnvironemnt extends PuppeteerEnvironment {
	async handleTestEvent( event ) {
		if ( event.name === 'test_fn_failure' ) {
			await this.global.jestPuppeteer.debug();
		}
	}
}

It does trigger the chrome’s debugger, but unfortunately, after resuming the debugger - browser just closes itself.

[sergtimosh]

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) It is the only way I can use debug Just like this:

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

})

[MatthiasEngh]

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 https://github.com/facebook/jest/issues/9359. You can use --testtimeoutnumber to test: https://jestjs.io/docs/en/cli#--testtimeoutnumber