Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Give karma.config.js access to command line arguments
See original GitHub issueCurrently, the config argument passed into karma.config.js is an empty object, that gets filled out. It would be beneficial, to have access to command line arguments from within the configuration, through the passed config object, as this would allow custom logic, based on those arguments to be applied.
Example scenario: There are two test suites (eg. unit and component) in two different folders. It’s desired to run only the selected test suite. This could easily be achieved by passing an argument on the command line (like suite=unit), that karma.config.js would have access to and would set the proper value on the config.files property.
What do people think about it? The implementation of this would be very straightforward (basically a one-liner).
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This would definitely be useful, such as for turning on/off coverage instrumentation via commandline when using non-standard processors like webpack.
Thanks @Dignifiedquire @danielcompton.
I figured out after posting that it’s mentioned in the OP (resolved config is under
config.*).