I can see this project is no longer maintained, but I'm just wondering if anyone here has any recommendations for my dilemma right now.
I currently have karma set up with Istanbul code coverage tool. This is great as we like to see what % of our codebase is covered by unit tests. We are mostly using 'protractor-cucumber-framework' to run gherkin scenarios with ui / web tests in the step definitions. However, we would like to implement some of our step definitions as unit tests, and for that it's really awesome to have cucumber reports generated. It is possible to have both types of reports generated? Does it make sense to still generate code coverage from you step definitions? Should I have cucumber-karma tests and regular karma unit tests or can I all-out switch over to cucumber-karma tests? Awesome project. I'm just trying to figure out the best way to fit it into our development process.
Thanks,
Jim
Hi,
I can see this project is no longer maintained, but I'm just wondering if anyone here has any recommendations for my dilemma right now.
I currently have karma set up with Istanbul code coverage tool. This is great as we like to see what % of our codebase is covered by unit tests. We are mostly using 'protractor-cucumber-framework' to run gherkin scenarios with ui / web tests in the step definitions. However, we would like to implement some of our step definitions as unit tests, and for that it's really awesome to have cucumber reports generated. It is possible to have both types of reports generated? Does it make sense to still generate code coverage from you step definitions? Should I have cucumber-karma tests and regular karma unit tests or can I all-out switch over to cucumber-karma tests? Awesome project. I'm just trying to figure out the best way to fit it into our development process. Thanks, Jim