-
-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better way to handle multiple unit testing frameworks #135
Comments
I would like to write-up a proposal for generators that can easily consume or build-on other generators. I feel like this is parallel to the unit-testing story as we ideally want generator-mocha and so on to be able to work more closely with framework generators. People want to be able to yo chromeapp angular karma and so on with it just working. Right now that's far off from what is capable of doing cleanly. |
What's current thinking on default test framework selection? I'd love to edit something like Most conversation seems focused on remembering a selection for a single prompt and a single generator. I'd rather declare a preference and never see the prompt for any generator in any project. |
The idea is that it should remember your selections using keywords in your local .yo-rc. But i would like to see it support having a global file where you could also define keyword values that should be applied to all generators. @SBoudrias what do you think? |
I would second global config also being supported. |
Sounds perfect :) |
Global config looks good to me too. Any idea on how this could be reflected on the end user interface? |
@SBoudrias we could add some common questions to |
Great idea my coworkers and I were contemplating the same thing. Here's a gist of something I started brainstorming up for the config/manifest idea: https://gist.github.com/elycruz/6429384 |
I feel like with composability and once #579 lands, we'll have all cards in hand to make it happen inside generator-karma. I'll close as it is really already done and should just be implemented in composable testing generator. |
We need to make it easier for generators to support multiple unit-testing frameworks.
Currently it's very static and hardcoded. Eg. #120
Any ideas?
The text was updated successfully, but these errors were encountered: