noExportsInTest

诊断类别：lint/suspicious/noExportsInTest

¥Diagnostic Category: lint/suspicious/noExportsInTest

JavaScript (and super languages)

自从：v1.6.0

¥Since: v1.6.0

来源：

¥Sources:

灵感来自：jest/no-export

¥Inspired from: jest/no-export

禁止在包含测试的文件中使用 export 或 module.exports

¥Disallow using export or module.exports in files containing tests

此规则旨在通过从测试文件中导出内容来消除重复的测试运行。如果你从测试文件导入，则该文件中的所有测试都将在每个导入的实例中运行，因此最重要的是，不要从测试中导出，而是在需要在测试之间共享辅助函数时将其移动到单独的文件中。

¥This rule aims to eliminate duplicate runs of tests by exporting things from test files. If you import from a test file, then all the tests in that file will be run in each imported instance, so bottom line, don’t export from a test, but instead move helper functions into a separate file when they need to be shared across tests.

示例

¥Examples

无效

¥Invalid

export function myHelper() {}
describe('a test', () => {
    expect(1).toBe(1);
});

code-block.js:1:1 lint/suspicious/noExportsInTest ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Do not export from a test file.
  
  > 1 │ export function myHelper() {}
      │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    2 │ describe(‘a test’, () => {
    3 │     expect(1).toBe(1);

有效

¥Valid

function myHelper() {}
describe('a test', () => {
    expect(1).toBe(1);
});

noExportsInTest

示例

无效

有效

相关链接