Protractor troubleshooting

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:

• 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?