Provide noInject option to prevent altering Cucumber .feature files #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've recently started using grunt-protractor-coverage with Cucumber style tests. Cucumber .feature files aren't written as JavaScript (they're plain text), so GPC fails when trying to rewrite them to call runCoverageGlobal.
To get around this, I've created a noInject option. When enabled GPC no longer tries to create these temporary rewritten features. I've also added a JS file that can be required from within the step definitions JS file and called to save coverage data - an example of it's use is provided in README.md
I'd welcome any comments/suggestions - thanks