You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guides/release/tutorial/part-1/automated-testing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,7 @@ Finally, we asserted that clicking on the link should bring us to the `/about` U
115
115
</div>
116
116
</div>
117
117
118
-
We can put our automated test into motion by running the _test server_ using the `ember test --server` command, or `ember t -s`forshort. This server behaves much like the development server, but it is explicitly running for our tests. It may automatically open a browser windowand take you to the test UI, or you can open `http://localhost:7357/` yourself.
118
+
We can put our automated test into motion by running the development server using the `npm start` commandand navigating to `http://localhost:4200/tests`in your browser.
119
119
120
120
If you watch really carefully, you can see our test robot roaming around our app and clicking links:
@@ -72,7 +72,7 @@ We're on a roll! While we're at it, let's add our third page. This time, things
72
72
We want to keep the existing URLs for the new website, but we don't want to have to type `getting-in-touch` all over the new codebase! Fortunately, we can have the best of both worlds:
@@ -69,14 +69,16 @@ Creating a new Ember app in /home/runner/work/super-rentals-tutorial/super-renta
69
69
create config/targets.js
70
70
create ember-cli-build.js
71
71
create .gitignore
72
+
create index.html
72
73
create package.json
73
74
create public/robots.txt
74
-
create testem.js
75
+
create testem.cjs
75
76
create tests/helpers/index.js
76
77
create tests/index.html
77
78
create tests/integration/.gitkeep
78
79
create tests/test-helper.js
79
80
create tests/unit/.gitkeep
81
+
create vite.config.mjs
80
82
81
83
Installing packages... This might take a couple of minutes.
82
84
npm: Installing dependencies ...
@@ -110,6 +112,8 @@ super-rentals
110
112
├── app
111
113
│ ├── components
112
114
│ │ └── .gitkeep
115
+
│ ├── config
116
+
│ │ └── environment.js
113
117
│ ├── controllers
114
118
│ │ └── .gitkeep
115
119
│ ├── helpers
@@ -124,7 +128,6 @@ super-rentals
124
128
│ │ └── application.gjs
125
129
│ ├── app.js
126
130
│ ├── deprecation-workflow.js
127
-
│ ├── index.html
128
131
│ └── router.js
129
132
├── config
130
133
│ ├── ember-cli-update.json
@@ -144,22 +147,25 @@ super-rentals
144
147
│ └── test-helper.js
145
148
├── .editorconfig
146
149
├── .ember-cli
147
-
├── .eslintcache
150
+
├── .env.development
148
151
├── .gitignore
149
152
├── .prettierignore
150
-
├── .prettierrc.js
153
+
├── .prettierrc.mjs
151
154
├── .stylelintignore
152
-
├── .stylelintrc.js
153
-
├── .template-lintrc.js
155
+
├── .stylelintrc.cjs
156
+
├── .template-lintrc.mjs
154
157
├── .watchmanconfig
155
158
├── README.md
159
+
├── babel.config.cjs
156
160
├── ember-cli-build.js
157
161
├── eslint.config.mjs
162
+
├── index.html
158
163
├── package.json
159
164
├── package-lock.json
160
-
└── testem.js
165
+
├── testem.cjs
166
+
└── vite.config.mjs
161
167
162
-
17 directories, 37 files
168
+
27 directories, 56 files
163
169
```
164
170
165
171
We'll learn about the purposes of these files and folders as we go. For now, just know that we'll spend most of our time working within the `app` folder.
@@ -172,11 +178,26 @@ Ember CLI comes with a lot of different commands for a variety of development ta
Build successful (9761ms) – Serving on http://localhost:4200/
189
+
190
+
Build successful (9761ms)
191
+
192
+
Slowest Nodes (totalTime >= 5%) | Total (avg)
193
+
-+-
194
+
Babel: @embroider/macros (1) | 436ms
195
+
196
+
197
+
198
+
VITE v6.3.6 ready in 4143 ms
199
+
200
+
➜ Local: http://localhost:4200/
180
201
```
181
202
182
203
The development server is responsible for compiling our app and serving it to the browsers. It may take a while to boot up. Once it's up and running, open your favorite browser and head to <http://localhost:4200>. You should see the following welcome page:
@@ -204,8 +225,8 @@ The development server has a feature called _live reload_, which monitors your a
204
225
As text on the welcome page pointed out, the source code for the page is located in `app/templates/application.gjs`. Let's try to edit that file and replace it with our own content:
0 commit comments