量角器故障排除 [英] Protractor troubleshooting
问题描述
在量角器1.5.0,有一个新的<一个href=\"https://github.com/angular/protractor/commit/8b5ae8ba3d2b3f1de75c0add91694e39e9c591a8\"><$c$c>--troubleshoot$c$c>旗的引入,这是不正确的时刻的记载,但在<一href=\"https://github.com/angular/protractor/blob/62cb775eb229ac6ce3af56cc283cc2ddd7605ae3/CHANGELOG.md\">changelog它指出:
In protractor 1.5.0, there was a new --troubleshoot
flag introduced, which is not properly documented at the moment, but in the changelog it states:
改进的错误信息,并添加调试信息时
Improve error messages and add debug info when
- 配置文件无法解析
- 一个会话的webdriver不能
启动 - 多个元素使用元素中找到
哪些用例确实 - 疑难解答
命令行参数覆盖
Which use cases does --troubleshoot
command-line argument cover?
我想问的原因是,这是一个有点混乱:
The reason I ask is that this is a bit confusing:
- 难道不应该被默认启用?因为如果有错误,如上面列出的,有关于错误的附加信息将是有益的。
- 也有相关的
- 详细
和- 堆栈跟踪
标志。他们是否也涉及到调试和故障排除?
- Should not it be enabled by default? Because if there are errors like listed above, having an additional information about the error would be helpful.
- There are also relevant
--verbose
and--stackTrace
flags. Are they also related to debugging and troubleshooting?
推荐答案
目前 - 排查
做了两件事:
- 它解析配置并提供建议
- 它打印出所有相关的环境变量(OS,量角器版本,架构,功能等),这样,当他们汇报的问题,其他人跟我一样可以看一下这个信息来确定问题是否与环境有关的。
目前, - 排查
旨在帮助谁的的用户无法量角器运行的(不用于解决失败的测试)。而且它更像是:
Right now, --troubleshoot
aims to help users who cannot get protractor to run (NOT for troubleshooting failed tests). And it's more like:
如果你不能得到量角器跑,冒这种模式下,看它是否抓到
提交问题之前,任何东西;如果没有,粘贴输出
从故障排除,所以我们不必问OS /版本的/ etc每
时间。
if you can't get protractor to run, run this mode to see if it catches anything before submitting an issue; if it doesn't, paste the output from troubleshoot so we don't have to ask about OS/version/etc every time.
话虽这么说,有计划添加额外的功能,以帮助用户解决他们的非运行的测试,在未来。
That being said, there are plans to add additional features to help users troubleshoot their non-running tests in the future.
这篇关于量角器故障排除的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!