Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
dirk-pieterse authored May 7, 2018
1 parent 1ecc79f commit ebed8eb
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/articles/documentation/test-api/assertions/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ checked: false
You can use *assertions* to check if the tested webpage's state matches your expectations.

TestCafe provides a comprehensive set of assertions that are based on the Behavior Driven Development style (BDD-style).
See [Assertion API](assertion-api.md).
See [Assertion API](assertion-api.md) for more information.

This topic consists of the following sections.
This topic consists of the following sections:

* [Assertion Structure](#assertion-structure)
* [Smart Assertion Query Mechanism](#smart-assertion-query-mechanism)
Expand All @@ -32,7 +32,7 @@ See [Smart Assertion Query Mechanism](#smart-assertion-query-mechanism) for deta
Next is an [assertion method](assertion-api.md). Assertion methods accept an expected value
and, optionally, other arguments.

For instance, the deep equality assertion has the following structure.
For instance, the deep equality assertion has the following structure:

```text
await t.expect( actual ).eql( expected, message, options );
Expand Down Expand Up @@ -158,4 +158,4 @@ In case this is what you need, set the `allowUnawaitedPromise` option to `true`.

```js
await t.expect(doSomethingAsync()).ok('check that a promise is returned', { allowUnawaitedPromise: true });
```
```

0 comments on commit ebed8eb

Please sign in to comment.