Protractor troubleshooting
Currently --troubleshoot does two things:
- It parses the config and provides suggestions on it
- It prints out all the relevant environment variables (OS, protractor version, framework, capabilities, etc) so that when they report the problems others like me can look at this information to identify if the issue is related to the environment.
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.