update all ember server to npm start

Author: mansona

guides/release/configuring-ember/configuring-ember-cli.md

@@ -1,7 +1,7 @@
 In addition to configuring your app itself, you can also configure Ember CLI.
 These configurations can be made by adding them to the `.ember-cli` file in your application's root. Many can also be made by passing them as arguments to the command line program.
 
-For example, a common desire is to change the port that Ember CLI serves the app from. It's possible to pass the port number from the command line with `ember server --port 8080`. To make this configuration permanent, edit your `.ember-cli` file like so:
+For example, a common desire is to change the port that Ember CLI serves the app from. It's possible to pass the port number from the command line with `ember server --port 8080`, if you want to pass the port to your `npm start` script you would pass it with an extra `--` like this: `npm start -- --port 8080`. To make this configuration permanent, edit your `.ember-cli` file like so:
 
 ```json
 {

guides/release/getting-started/quick-start.md

@@ -51,7 +51,7 @@ Let's make sure everything is working properly.
 
 ```bash
 cd ember-quickstart
-ember serve
+npm start
 ```
 
 After a few seconds, you should see output that looks like this:

guides/release/testing/index.md

@@ -16,18 +16,12 @@ You have a few options for running tests.
 
 First, you can run the test suite by entering the command `ember test`, or `ember t`, in your terminal. This will run the suite just once.
 
-Suppose, instead, you want the suite to run after every file change. You can enter `ember test --server`, or `ember t -s`.
-
-Lastly, if you are already running a local development server (through `ember server`), you can visit the `/tests` URI. This will render the `tests/index.html` template.
+Running a local development server (through `npm start`), you can visit the `/tests` URI. This will render the `tests/index.html` template. This will also auto-update as you are changing files in your app.
 
 ```bash
 # Run all tests once
 ember test
 ember t
-
-# Run all tests after every file change
-ember test --server
-ember t -s
 ```
 
 ### How to Filter Tests
@@ -38,23 +32,23 @@ The `--module` option allows you to select a **module**—a group of tests that
 
 ```bash
 # Button component example
-ember test --server --module="Integration | Component | simple-button"
+ember test --module="Integration | Component | simple-button"
 
 # Run tests for a location service
-ember t -s -m="Unit | Service | location"
+ember t -m="Unit | Service | location"
 ```
 
 The `--filter` option is more versatile. You can provide a phrase to match against the modules and test descriptions. A test description is what appears in `test()` in QUnit.
 
 ```bash
 # Button component example
-ember test --server --filter="should show icon and label"
+ember test --filter="should show icon and label"
 
 # Test everything related to your dashboard
-ember t -s -f="Dashboard"
+ember t -f="Dashboard"
 
 # Run integration tests
-ember t -s -f="Integration"
+ember t -f="Integration"
 ```
 
 In QUnit, you can exclude tests by adding an exclamation point to the beginning of the filter, e.g. `ember test --filter="!Acceptance"`.

guides/release/testing/testing-application.md

@@ -148,7 +148,7 @@ During the development of your tests or when you refactor your application's cod
 To try them out, do the following steps:
 
 1. Add `await pauseTest();` in your test code.
-2. Run `ember server`.
+2. Run `npm start`.
 3. Visit `http://localhost:4200/tests` in your browser
 
 When the execution of the test come upon `await pauseTest()`, the test will be paused, allowing you to inspect the state of your application.