QUnit Blueprints Quest Issue

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 ember-cli@2.17), 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 of setupApplicationTest 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 current ember-cli codebase. We should work with @rwjblue and the learning team (cc @locks) to determine how we best teach this.

Tasks

• (🔒 @Turbo87) Extend test-framework-detector.js to support a directory called qunit-rfc-232-files which will be where the “Simplified QUnit” blueprints will live in each of the blueprint test folders (e.g blueprints/component-test/qunit-rfc-232-files/). The decision to use the qunit-rfc-232-files directory should be based on the host’s ember-cli-qunit
• Add <type>-test “simplified QUnit” blueprints
  • acceptance-test - https://github.com/emberjs/ember.js/issues/15999
  • (🔒 @Turbo87) component-test
  • (🔒 @snewcomer) controller-test
  • (🔒 @snewcomer) helper-test
  • (🔒 @snewcomer) initializer-test
  • (🔒 @snewcomer) instance-initializer-test
  • (🔒 @boyanyordanov) mixin-test
  • (🔒 @rwwagner90) route-test
  • (🔒 @boyanyordanov) service-test
  • (🔒 @snewcomer) util-test
• (🔒 @alexander-alvarez) Extract the above tests blueprints into a standalone polyfill addon https://github.com/alexander-alvarez/ember-qunit-nested-module-blueprints-polyfill so developers can access the new testing blueprints regardless of what version of ember-cli they are on (so long as they are running ember-cli-qunit@^4.1.1)
• (🔒 @jessica-jordan) Update testing section in https://github.com/emberjs/guides to reflect new style (note this should land very close to when the changes above are implemented)

---

To pick up one of these items, please comment below and we’ll update the checklist with :lock: @your-name-here…

[jayjayjpg]

@rwjblue Personally, I’m happy to track it here, but I’m good with either solution

[rwjblue]

Looks good, I think all if the polyfill addon PRs are merged at this point.

Now only think left is the acceptance-test blueprint which we can do once https://github.com/emberjs/ember-qunit/pull/302 is reviewed and released.