I have an issue of the "oddly specific" variety. For a specific repo, my team decided that they would keep our protractor configuration in e2e/protractor.conf.js. This protractor configuration works fine from the command-line and within VSCode, but gives me issues as a WebStorm user. Specifically, I was having trouble debugging protractor tests within the IDE with this configuration.
I did some additional investigation, and I was able to work around the problem by doing the following:
- Move the protractor.conf.js file into the root of the repository
- Update all the relative paths in the protractor.conf.js file accordingly
Here is my question: Does WebStorm mandate that the protractor.conf.js file be placed in the root of the repository/project? If so, what would be the recommended way for me to correct this? It is unlikely that I'm going to be able to persuade a larger group of VSCode users to move this file.