Jest-Puppeteer 测试随机失败且没有输出

Jon*_* S. 6 jestjs jest-puppeteer

我有以下测试用例:

\n
it('User can logout', async () => {\n    await helper.navClick('.header-user-action__logout');\n    const url = page.url();\n    console.log(url)\n    await expect(url).toContain('auth');\n});\n
Run Code Online (Sandbox Code Playgroud)\n

helper.navClick只是一个小包装:

\n
async function navClick(selector, options) {\n    return await Promise.all([page.waitForNavigation(), expect(page).toClick(selector, options)]);\n}\n
Run Code Online (Sandbox Code Playgroud)\n

大多数时候,它会成功,没有任何问题,但有时会被标记为失败:

\n
    \xe2\x9c\x95 User can logout (569 ms)\n\n  \xe2\x97\x8f Login \xe2\x80\xba User can logout\n\n\n\n\n\n  console.log\n    https://auth.example.com/auth/realms/example/protocol/openid-connect/auth?response_type=code&client_id=example-app&redirect_uri=https%3A%2F%2Fexample.com%2Fsso%2Flogin&state=807469fd-3ee5-4d93-8354-ca47a63e69a6&login=true&scope=openid\n\n
Run Code Online (Sandbox Code Playgroud)\n

怎么会发生这种事呢?该网址多次包含“auth”,并且我没有看到任何其他可能导致测试失败的内容。

\n

Jon*_* S. 5

我通过设置自定义环境发现了这个问题:

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

class DebugEnv extends PuppeteerEnvironment {

    async handleTestEvent(event, state) {
        const ignoredEvents = ['setup', 'add_hook', 'start_describe_definition', 'add_test', 'finish_describe_definition', 'run_start',
            'run_describe_start', 'test_start', 'hook_start', 'hook_success', 'test_fn_start', 'test_fn_success', 'test_done',
            'run_describe_finish', 'run_finish', 'teardown'];
        if (!ignoredEvents.includes(event.name)) {
            console.log(new Date().toString() + " Unhandled event(" + event.name + "): " + util.inspect(event));
        }
    }
}

module.exports = DebugEnv;
Run Code Online (Sandbox Code Playgroud)

在我的中package.json,我将其设置testEnvironmentDebugEnv

"jest": {
    "preset": "jest-puppeteer",
    "testEnvironment": "./debugenv.js",
Run Code Online (Sandbox Code Playgroud)

通过这样做,我发现了一个与测试本身无关的错误(如果我没记错的话,与网络有关)。