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
- the configuration file cannot be parsed
- a webdriver session cannot be started
- more than one element is found using element
Which use cases does --troubleshoot
command-line argument cover?
The reason I ask is that this is a bit confusing:
--verbose
and --stackTrace
flags. Are they also related to debugging and troubleshooting?Protractor launched in 2013 before WebDriver APIs were standard and E2E tests were hard to write, and it tests Angular and AngularJS apps by running them in Google Chrome. It will continue to run until the end of 2022 when Angular 15 will be the last update.
Protractor Will Be Deprecated Some of the reasons behind these deprecation plans are: State of Protractor. Protractor is dependent on selenium-webdriver , and is not able to upgrade to the new version without introducing a huge breaking change, and forcing users to do a migration for all their tests.
Currently --troubleshoot
does two things:
Right now, --troubleshoot
aims to help users who cannot get protractor to run (NOT for troubleshooting failed tests). And it's more like:
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With