Using cucumber, scripts exception ends in a passing test

使用报告的 CodeceptJS 3.0.4 配置复现该故障，重点关注在 gherkin 部分中配置的 gherkin features 和 steps，并在 UI 和 headless 两种模式下进行。跟踪来自 Cucumber step 的 JavaScript 异常是如何报告的；当 scenario 失败且该异常在两种执行模式下都被记录到日志中时，即视为完成。

What are you trying to achieve?

I am using cucumber to write the tests.

A step for some reasons throws a javascript exception.

What do you get instead?

The scenario execution stops without any log, and test is considered as "passing".

This happens whenever I use the UI executor or the headless mode.

Details

• CodeceptJS version: 3.0.4
• NodeJS Version: 14.15.4
• Operating System:
• puppeteer
• Configuration file:

require('ts-node/register');
const { setHeadlessWhen, setSharedCookies } = require('@codeceptjs/configure');

// turn on headless mode when running with HEADLESS=true environment variable
// export HEADLESS=true && npx codeceptjs run
setHeadlessWhen(process.env.HEADLESS);
setSharedCookies();

process.env.TEST_URL = process.env.TEST_URL || 'http://localhost:3000';

// eslint-disable-next-line no-undef
exports.config = {
  tests: './test/**/*.test.ts',
  output: './output',
  helpers: {
    Puppeteer: {
      url: process.env.TEST_URL,
      show: true,
      browser: 'chromium',
      chrome: {
        args: ['--no-sandbox'],
      },
    },
    REST: {
      endpoint: `${process.env.TEST_URL}/api`,
    },
  },
  include: {
    I: './steps_file.ts',
  },
  bootstrap: null,
  mocha: {
    reporterOptions: {
      mochaFile: 'reports/e2e/community-management-web.xml',
    },
  },
  name: 'xxx-e2e',
  plugins: {
    pauseOnFail: {},
    retryFailedStep: {
      enabled: true,
    },
    tryTo: {
      enabled: true,
    },
    screenshotOnFail: {
      enabled: true,
    },
    allure: {
      enabled: false,
    },
  },
  gherkin: {
    features: './test/features/*.feature',
    steps: [
      './test/step-definitions/base.steps.ts',
      './test/step-definitions/xxx.steps.ts',
      './test/step-definitions/auth.steps.ts'
    ],
  },
};