From T324857: The Web App Testing Guidebook (pdf version).
Page 76:
- It’s easier to write (in my opinion, you’re welcome to disagree)
- You get better error messages
- It automatically retries failed assertions
Page 79:
One final note for now on this. Aside from the WebdriverIO specific assertions expect-webdriverio
adds, you also gain access to the built-in ExpectJS assertions.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T210726 Selenium framework maintenance | |||
| Open | None | T324685 Upgrade WebdriverIO to v8 in all repositories | |||
| Open | None | T325740 Replace Node.js Assert library with WebdriverIO Expect library | |||
| Resolved | Nik.xyz.in | T331484 Change `assert` to `expect` in WikiLambda browser tests |
Change 951069 had a related patch set uploaded (by Jakob; author: Jakob):
[wikibase/termbox@master] Use `expect` instead of `assert` for browser tests
Change 951062 had a related patch set uploaded (by Jakob; author: Jakob):
[mediawiki/extensions/Wikibase@master] Use `expect` instead of `assert` for browser tests
Change 951062 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Use `expect` instead of `assert` for browser tests
Change 951069 merged by jenkins-bot:
[wikibase/termbox@master] Use `expect` instead of `assert` for browser tests