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.

Description

In the Getting Started - How to Use the Guides section, the link for Ember CLI points to Configuration - Configuring Ember CLI section. The latter (configuring your app ) is an advanced topic and doesn't show much information.

Please link to the CLI Guides (https://cli.emberjs.com/release/) instead.

TODOs

• Update the Markdown file `guides/release/getting-