事件:'test:fail'

\Event: 'test:fail'

• data <Object>

  • column <number> | <undefined> 定义测试的列号,如果测试是通过 REPL 运行的,则为 undefined。

    \column <number> | <undefined> The column number where the test is defined, or undefined if the test was run through the REPL.

  • details <Object> 额外的执行元数据。

    \details <Object> Additional execution metadata.

    • duration_ms <number> 以毫秒为单位的测试持续时间。

      \duration_ms <number> The duration of the test in milliseconds.

    • error <Error> 封装测试引发的错误的错误。

      \error <Error> An error wrapping the error thrown by the test.

      • cause <Error> 测试抛出的实际错误。

        \cause <Error> The actual error thrown by the test.

    • type <string> | <undefined> 测试的类型,用于指示这是否是一个套件。

      \type <string> | <undefined> The type of the test, used to denote whether this is a suite.

    • attempt <number> | <undefined> 测试运行的尝试次数,仅在使用 --test-rerun-failures 标志时显示。

      \attempt <number> | <undefined> The attempt number of the test run, present only when using the --test-rerun-failures flag.

  • file <string> | <undefined> 测试文件的路径,如果测试是通过 REPL 运行的,则为 undefined。

    \file <string> | <undefined> The path of the test file, undefined if test was run through the REPL.

  • line <number> | <undefined> 定义测试的行号,如果测试是通过 REPL 运行的,则为 undefined。

    \line <number> | <undefined> The line number where the test is defined, or undefined if the test was run through the REPL.

  • name <string> 测试名称。

    \name <string> The test name.

  • nesting <number> 测试的嵌套级别。

    \nesting <number> The nesting level of the test.

  • testNumber <number> 测试的序号。

    \testNumber <number> The ordinal number of the test.

  • todo <string> | <boolean> | <undefined> 如果调用 context.todo,则存在

    \todo <string> | <boolean> | <undefined> Present if context.todo is called

  • skip <string> | <boolean> | <undefined> 如果调用 context.skip,则存在

    \skip <string> | <boolean> | <undefined> Present if context.skip is called

测试失败时触发。该事件保证按照测试定义的顺序触发。对应的执行命令事件为 'test:complete'。

\Emitted when a test fails. This event is guaranteed to be emitted in the same order as the tests are defined. The corresponding execution ordered event is 'test:complete'.