development/deno
development/deno
1
0
Fork 0
mirror of https://github.com/denoland/deno synced 2024-10-13 11:32:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typo assertAsyncThrows -> assertThrowsAsync (#7506)

Browse source
This commit is contained in:
Sidd Sridharan 2020-09-16 03:31:12 -07:00 committed by GitHub
parent 35ed3ce8d9
commit aa81bc73d9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/testing/assertions.md
View file

@ -139,13 +139,13 @@ Deno.test("Test Assert Not Match", () => {
### Throws
There are two ways to assert whether something throws an error in Deno,
`assertThrows()` and `assertAsyncThrows()`. Both assertions allow you to check
`assertThrows()` and `assertThrowsAsync()`. Both assertions allow you to check
an
[Error](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error)
has been thrown, the type of error thrown and what the message was.
The difference between the two assertions is `assertThrows()` accepts a standard
function and `assertAsyncThrows()` accepts a function which returns a
function and `assertThrowsAsync()` accepts a function which returns a
[Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
The `assertThrows()` assertion will check an error has been thrown, and
@ -164,7 +164,7 @@ Deno.test("Test Assert Throws", () => {
});
```
The `assertAsyncThrows()` assertion is a little more complicated, mainly because
The `assertThrowsAsync()` assertion is a little more complicated, mainly because
it deals with Promises. But basically it will catch thrown errors or rejections
in Promises. You can also optionally check for the error type and error message.