NG测试不再通过V14中的JEST CLI选项?

发布于 2025-02-10 15:03:02 字数 1488 浏览 2 评论 0 原文

我使用的是与角(而不是业力)的玩笑。 angular.json 文件似乎已正确配置为运行 ng test 工作。

根据

您可以在构建器选项中指定开玩笑的CLI选项(有用 当它是持续的config)或 ng test 作为参数的权利 (当它是单次计时器时)。

例如,运行一个测试:

ng测试-TestNamePattern =“我的测试套件我的测试用例”

这在我的V14升级之前正在工作,但事实并非如此。现在如果我运行:

ng test --testNamePattern="MyComponent"

我得到:

Error: Unknown argument: testNamePattern
Angular CLI: 14.0.2
Node: 16.13.1
Package Manager: yarn 1.22.17 
OS: darwin arm64

Angular: 14.0.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, language-service, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1400.2
@angular-devkit/build-angular   14.0.2
@angular-devkit/core            14.0.2
@angular-devkit/schematics      8.3.29
@schematics/angular             14.0.2
rxjs                            6.6.7
typescript                      4.7.4

注意:这可能是构建器的回归

I am using Jest with Angular (instead of Karma). The angular.json file seems to be configured properly, as running ng test works.

According to this article:

You can specify Jest CLI options either in builder options (useful
when it is a persistent config) or right to ng test as a parameter
(useful when it is a one-timer).

For example to run a single test:

ng test --testNamePattern="My test suite My test case"

This was working before my v14 upgrade, but this is not the case any more. Now if I run:

ng test --testNamePattern="MyComponent"

I get:

Error: Unknown argument: testNamePattern
Angular CLI: 14.0.2
Node: 16.13.1
Package Manager: yarn 1.22.17 
OS: darwin arm64

Angular: 14.0.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, language-service, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1400.2
@angular-devkit/build-angular   14.0.2
@angular-devkit/core            14.0.2
@angular-devkit/schematics      8.3.29
@schematics/angular             14.0.2
rxjs                            6.6.7
typescript                      4.7.4

Note: this is possibly a regression of the builder

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

白鸥掠海 2025-02-17 15:03:02

好的,引用 @just-jeb来自github

移民指南< /a>。这是一个破裂的变化
角CLI,而不是建造者。骆驼的论点不再是
支持。


因此,这是运行“ myComponent”测试注意的正确方法

ng test --test-name-pattern="MyComponent"

jetbrains尚未(28.06)。 2022)支持烤肉串案例参数

Okay quoting @just-jeb from github

It's mentioned in the migration guide. It's a breaking change of
Angular CLI, not the builder. camelCase arguments are no longer
supported.

Here is therefore the proper way to run the "MyComponent" test

ng test --test-name-pattern="MyComponent"

Note: Jetbrains does not yet (28.06.2022) supports the kebab case arguments

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文