Skip to content
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 RFC 232 variant detector for mocha & component blueprints #16865

Merged
merged 1 commit into from
Sep 4, 2018

Conversation

Dhaulagiri
Copy link
Contributor

@Dhaulagiri Dhaulagiri commented Aug 5, 2018

Addresses #16863 by adding logic to detect when rfc 232-style tests should be used with ember-mocha 0.14 and adds component rendering and unit test blueprints

@Dhaulagiri Dhaulagiri changed the title Add RFC 232 variant detector for mocha & component tests Add RFC 232 variant detector for mocha & component blueprints Aug 5, 2018
@Dhaulagiri
Copy link
Contributor Author

@Turbo87 @rwjblue I'd like to get some momentum behind the remaining items in the quest issue, but I don't want to get too far before validating that the work in this PR is the right direction. Can you let me know any feedback??

Copy link
Contributor

@simonihmig simonihmig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

@kateeliza24
Copy link

kateeliza24 commented Aug 17, 2018 via email

@Dhaulagiri
Copy link
Contributor Author

One thing I noticed is that it may be worth holding this until all the tests are converted. The way this is written, if a type of test hasn't been converted no test file will be generated since the blueprints won't exist.

@Dhaulagiri
Copy link
Contributor Author

Dhaulagiri commented Aug 18, 2018

Actually, my comment above is not accurate. I was trying to generate a mixin test but that doesn't actually exist for even the previous version of mocha tests 🤷‍♂️ . I'll carry on doing these one at a time with the intention of getting them all done soon regardless.

@Turbo87
Copy link
Member

Turbo87 commented Aug 18, 2018

@Dhaulagiri looks good in general, but keep in mind that ember-cli-mocha should eventually also support this new style.

@Dhaulagiri
Copy link
Contributor Author

@Turbo87 that is good to know, I was under the impression that going forward one would simply use ember-mocha directly and not use ember-cil-mocha`. Would it be worth accounting for that right now as part of this effort or should we tackle that separately?

I'll try to get a separate discussion going at some point, but it seems like we could also deprecate and remove the pre 0.12 blueprints since it has been quite a long time since those were the default.

@Turbo87
Copy link
Member

Turbo87 commented Aug 18, 2018

I was under the impression that going forward one would simply use ember-mocha directly and not use ember-cil-mocha

eventually that should be possible, but right now ember-cli-mocha contains the blueprints that automatically adjust the tests/test-helper.js to use Mocha instead of QUnit, and some older versions of e.g. ember-cli-eslint are not aware of ember-mocha being a viable option.

that said, the blueprints in ember-cli-mocha are not up-to-date with the changes in ember-mocha yet, which is precisely the reason why there is no current release yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants