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: CHANGELOG.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,7 +136,7 @@ plug
136
136
Mix also includes `mix escript.install` and `mix escript.uninstall` tasks for managing escripts. The tasks was designed in a way to mimic the existing `mix archive` functionality except that:
137
137
138
138
* Archives must be used sparingly because every new archive installed affects Mix performance, as every new archive is loaded when Mix boots. Escripts solve this by being managed apart from your Elixir/Mix installed
139
-
* Archives depends on the current Elixir version. Therefore, updating your Elixir version may break an archive. Fortunately, escripts bundle Elixir inside themselves, and therefore do not depend on your Elixir system version
139
+
* Archives depends on the current Elixir version. Therefore, updating your Elixir version may break an archive. Fortunately, escripts include Elixir inside themselves, and therefore do not depend on your Elixir system version
140
140
141
141
Escripts will be installed at `~/.mix/escripts` which must be added to your [`PATH` environment variable](https://en.wikipedia.org/wiki/PATH_(variable)).
142
142
@@ -214,15 +214,15 @@ At the end of the run, ExUnit will also report it as a property, including both
214
214
1 property, 10 tests, 0 failures
215
215
```
216
216
217
-
### Named setups and bundles
217
+
### Named setups and describes
218
218
219
-
Finally, ExUnit v1.3 includes the ability to organize tests together in bundles:
219
+
Finally, ExUnit v1.3 includes the ability to organize tests together in describe blocks:
220
220
221
221
```elixir
222
222
defmoduleStringTestdo
223
223
useExUnit.Case, async:true
224
224
225
-
bundle"String.capitalize/2"do
225
+
describe"String.capitalize/2"do
226
226
test "uppercases the first grapheme"do
227
227
assert "T"<>_=String.capitalize("test")
228
228
end
@@ -234,25 +234,25 @@ defmodule StringTest do
234
234
end
235
235
```
236
236
237
-
Every test inside a bundle will be tagged with the bundle name. This allows developers to run tests that belong to particular bundles, be them in the same file or across many files:
237
+
Every test inside a describe block will be tagged with the describe block name. This allows developers to run tests that belong to particular blocks, be them in the same file or across many files:
238
238
239
239
```
240
-
$ mix test --only bundle:"String.capitalize/2"
240
+
$ mix test --only describe:"String.capitalize/2"
241
241
```
242
242
243
-
Note bundles cannot be nested. Instead of relying on hierarchy for composition, we want developers to build on top of named setups. For example:
243
+
Note describe blocks cannot be nested. Instead of relying on hierarchy for composition, we want developers to build on top of named setups. For example:
244
244
245
245
```elixir
246
246
defmoduleUserManagementTestdo
247
247
useExUnit.Case, async:true
248
248
249
-
bundle"when user is logged in and is an admin"do
249
+
describe"when user is logged in and is an admin"do
250
250
setup [:log_user_in, :set_type_to_admin]
251
251
252
252
test ...
253
253
end
254
254
255
-
bundle"when user is logged in and is a manager"do
255
+
describe"when user is logged in and is a manager"do
256
256
setup [:log_user_in, :set_type_to_manager]
257
257
258
258
test ...
@@ -264,7 +264,7 @@ defmodule UserManagementTest do
264
264
end
265
265
```
266
266
267
-
By forbidding hierarchies in favor of named setups, it is straight-forward for the developer to glance at each bundle and know exactly the setup steps involved.
267
+
By forbidding hierarchies in favor of named setups, it is straight-forward for the developer to glance at each describe block and know exactly the setup steps involved.
268
268
269
269
## v1.3.0-dev
270
270
@@ -320,7 +320,7 @@ By forbidding hierarchies in favor of named setups, it is straight-forward for t
320
320
*[ExUnit] Raise a straight-forward error message in case a duplicate test name is defined
321
321
*[ExUnit] Bump the default number of max cases to double of schedulers to support both IO and CPU bound tests
322
322
*[ExUnit] Support for named setups in `setup` and `setup_all`
323
-
*[ExUnit] Support for bundling tests together with `bundle/2`
323
+
*[ExUnit] Support for bundling tests together with `describe/2`
0 commit comments