We really should be appending the DOM nodes into #qunit-fixture especially for things that require running the browsers HTML parser.

Relevant conversation here: hjdivad/ember-m3#807

We should have a test that validates each service can actually be resolved from the container (within a scope). See #339 for motivation. It would be fantastic if this could be done via reflection and not manually adding a new test every time you register a new service. I'm thinking we would define a static member that contained all the ServiceDescriptors. Then in the test we just get this member

We are no longer using the ember slack. Bonus points for notifying a bot on Discord.

• http://hangaroundtheweb.com/2019/10/creating-runtime-assisted-codemods-using-telemetry-helpers/
• http://hangaroundtheweb.com/2020/05/setting-up-coveralls-for-your-ember-addons/
• http://medium.com/@nowims/moving-from-react-to-ember-2020-86e082477d45
• http://www.balinterdi.com/blog/built-in-input-helpers-in-ember-js-when-and-whether-they-should-be-used
• https://0xadada.

This issue is good for beginners. Read Making your first pull request and ask for help if you run into issues! Experienced contributors are asked to search for other things to fix.

In [this guide](https://github.com/ember-learn/guides-source/blob/master/guides/release/templates/input-hel