-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add acceptance tests for the mocha blueprints #4187
Conversation
It looks like the blueprints on Windows are actually being generated with Should I adjust the tests to not test the line breaks for now or change AppVeyor to always use the original line breaks? |
ce42407
to
1e1eec0
Compare
rebased on top of #4189 to solve the line ending issues |
Do you mind rebasing this pr @Turbo87 |
1e1eec0
to
8008837
Compare
@bmac done |
@Turbo87 this looks good. Can you please squash into 1 commit? |
Update "ember-cli-blueprint-test-helpers" to v0.9.0 node-tests/blueprints/model: Add test for "mocha" blueprint node-tests/blueprints/adapter: Add test for "mocha" blueprint node-tests/blueprints/serializer: Add test for "mocha" blueprint node-tests/blueprints/transform: Add test for "mocha" blueprint
8008837
to
d65804f
Compare
@pangratz done |
Add acceptance tests for the mocha blueprints
🎉 |
@pangratz out of curiosity, what is the reason for squashing the commits all the time? |
I can only speak for myself but I can think of the following reasons:
|
👍 although it would manageable 😉
GitHub actually allows you to just revert the merge commit
I personally try to keep the commits as small as possible to make them easier to review and then limit the PRs to single, specific features
granted, although since we're still using non-fast-forward merge commits the history graph isn't entirely clean anyway
sure, that's essentially the reason why I'm not complaining, just asking 😉 |
No description provided.