IntelliJ Shorten Command Line for Cucumber Tests(IntelliJ 缩短 Cucumber 测试的命令行)
问题描述
我在 IntelliJ 中运行 Cucumber 测试时遇到了问题.当我尝试运行某个功能或场景时,我收到以下错误:
"错误运行'Feature <feature>': 命令行太长.缩短 Feature: <feature> 或 Cucumber java 默认配置的命令行"
我知道作为 IntelliJ 的一部分
I've encountered an issue running Cucumber tests in IntelliJ. When I try to run a feature or scenario, I get the following error:
"Error running 'Feature <feature>': Command line is too long. Shorten command line for Feature: <feature> or also for Cucumber java default configuration"
I know as part of IntelliJ's 2017.3 release, they added support for a "Shorten Command Line" option in the Run/Debug Configurations. However, if I compare the default configs, I don't see it as part of the Cucumber Java configuration, but I do see it in the JUnit configuration for example.
I don't get the popup tip that others have mentioned about the dynamic .classpath, I'm assuming because of this new release. Any ideas?
If you edit IntelliJ's workspace.xml file to set the dynamic.classpath
property to true, it will work.
<component name="PropertiesComponent">
...
<property name="dynamic.classpath" value="true" />
</component>
I believe IntelliJ used to do this via a popup for you, but since the "Shorten Command Line" feature in 2017.3 has been added to the normal default Run/Debug configurations, it no longer does it this way. And since Cucumber for Java is a plugin, it must not know what to do in that scenario.
Hopefully the issue is fixed to add the dropdown:
Found some of the answer here: IDEA 10.5 Command line is too long
这篇关于IntelliJ 缩短 Cucumber 测试的命令行的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:IntelliJ 缩短 Cucumber 测试的命令行


- java.lang.IllegalStateException:Bean 名称“类别"的 BindingResult 和普通目标对象都不能用作请求属性 2022-01-01
- Eclipse 的最佳 XML 编辑器 2022-01-01
- 未找到/usr/local/lib 中的库 2022-01-01
- 转换 ldap 日期 2022-01-01
- 将 Java Swing 桌面应用程序国际化的最佳实践是什么? 2022-01-01
- 在 Java 中,如何将 String 转换为 char 或将 char 转换 2022-01-01
- 如何指定 CORS 的响应标头? 2022-01-01
- 如何使 JFrame 背景和 JPanel 透明且仅显示图像 2022-01-01
- 获取数字的最后一位 2022-01-01
- GC_FOR_ALLOC 是否更“严重"?在调查内存使用情况时? 2022-01-01