-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
QUnit Blueprints Quest Issue #15933
Comments
Awesome, thanks for organizing this @alexander-alvarez! |
@alexander-alvarez should we use |
also I'm wondering if we should do the implementation in https://github.com/alexander-alvarez/ember-qunit-nested-module-blueprints-polyfill first and once those are solid we can import them here |
@Turbo87 - I'd prefer to land the "real" implementations first (so that the polyfill truly is a polyfill). If that turns out to be costly (or I'm too much of a blocker in landing PR's) we can swap to targeting the polyfill addon first... |
OK, first implementation is done and landed (along with the test framework detector changes required to support the path forward). The game is afoot! |
Doing the |
@rwjblue I'm always happy to work on blueprints. Want to assign a couple my way? |
@rwwagner90 choose one and announce it here, so that others are not doing the same work too :) |
@Turbo87 I'm not picky, but I'll randomly choose |
Updated description:
|
Tackling controller && initializer && instance-initializer tests in 3 separate PR's! |
If there's anything left I could take one. |
@christophermlne mixin, service, and |
Taking the utils. @christophermlne lmk if you want to tackle that one or want to take on either service or mixin! |
I will try to do mixin and if I manage I will look into service as well. |
@boyanyordanov don't worry, we're here to help you if you have questions :) |
I'll go ahead and add a PR for service-test too. |
This updates the testing section about helpers according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the controller testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the route testing section according to the new Ember QUnit testing patterns proposed in RFC#232.
This updates the model testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the introduction into testing introducing new concepts of the Ember Qunit testing API proposed in RFC#232 and RFC#268.
This updates the title of the former "Unit Testing Basics" section to "Testing Basics" to avoid talking about "container" tests in an originally "unit" test focused section.
This updates the integration testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the testing section about helpers according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the controller testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the route testing section according to the new Ember QUnit testing patterns proposed in RFC#232.
This updates the model testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the introduction into testing introducing new concepts of the Ember Qunit testing API proposed in RFC#232 and RFC#268.
This updates the title of the former "Unit Testing Basics" section to "Testing Basics" to avoid talking about "container" tests in an originally "unit" test focused section.
This updates the controller testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the route testing section according to the new Ember QUnit testing patterns proposed in RFC#232.
This updates the model testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the introduction into testing introducing new concepts of the Ember Qunit testing API proposed in RFC#232 and RFC#268.
This updates the title of the former "Unit Testing Basics" section to "Testing Basics" to avoid talking about "container" tests in an originally "unit" test focused section.
This updates the acceptance testing section including its code examples according to the new Ember Qunit Pattern proposed through RFC#268.
This updates the unit testing section including code examples according to the new Ember Qunit Testing Patterns proposed in RFC#232.
This updates the integration testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the testing section about helpers according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the controller testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the route testing section according to the new Ember QUnit testing patterns proposed in RFC#232.
This updates the model testing section according to the new Ember Qunit testing patterns proposed in RFC#232.
This updates the introduction into testing introducing new concepts of the Ember Qunit testing API proposed in RFC#232 and RFC#268.
This updates the title of the former "Unit Testing Basics" section to "Testing Basics" to avoid talking about "container" tests in an originally "unit" test focused section.
Thanks everyone for your hard work here! |
Background
We need to implement changes in blueprints and docs realted to RFC 232 and RFC 268.
(Some background for those unfamiliar http://rwjblue.com/2017/10/23/ember-qunit-simplication/)
As of
ember-cli-qunit@^4.1.1
(which is in the default blueprint as of[email protected]
), we can implement the "Simplified QUnit" style tests in all tests except for acceptance tests.In a future release of
ember-qunit
(likely 3.2.x), we will be able to leverage the implementation ofsetupApplicationTest
from RFC 268 for use in acceptance-tests. Once these changes are implemented upstream, we must implement the blueprint updates.Currently, we have no way to generate these test files but we can run the
ember-qunit-codemod
to migrate test files and continue to iterate on the final output in the blueprint specific pull requests.The desired behavior when generating testing blueprints is to, generate "Simplified QUnit" style tests if supported by the host app. We have several tasks below to extend the blueprints to support the "Simplified QUnit" style blueprints alongside the legacy, and ember-mocha blueprints. We can likely add to the behavior of
test-framework-detector.js
to support this other extension. Once these changes are completed we also need to update the guides to be consistent with the currentember-cli
codebase. We should work with @rwjblue and the learning team (cc @locks) to determine how we best teach this.Tasks
test-framework-detector.js
to support a directory calledqunit-rfc-232-files
which will be where the "Simplified QUnit" blueprints will live in each of the blueprint test folders (e.gblueprints/component-test/qunit-rfc-232-files/
). The decision to use thequnit-rfc-232-files
directory should be based on the host'sember-cli-qunit
<type>-test
"simplified QUnit" blueprintsember-cli
they are on (so long as they are runningember-cli-qunit@^4.1.1
)To pick up one of these items, please comment below and we'll update the checklist with
:lock: @your-name-here
...The text was updated successfully, but these errors were encountered: