Kris Kaczor

Current message says: `Mock is not configured`. This should provide info about parameters because mock can be configured for some but not for others.

ES6's proxies can't be compared with `expect.anything`

``` const mock = mockFn() .resolvesToOnce(1) .resolvesToOnce(2) .resolvesToOnce(3) .resolvesTo(4); console.log(mock()) // returns 4 ?????? ```

Investigate if we can support catching async error like this: CC: @7sne ```typescript expect(async () => asyncMethod()).toThrow( Error, 'Assertion Error: Call stack should be empty by the end of the...

Docs overhaul

4

TODO: - [x] upgrade docozaurus - [ ] add searchbox - [ ] add example to the main page: Releated: https://github.com/dethcrypto/earl/issues/142 - [ ] add somewhere link to the changelog...

https://github.com/sinonjs/fake-timers we should decide if we want to incorporate this into the core or at least document how to use it with earl

A very basic approach to testing types could look like this: https://twitter.com/devanshj__/status/1495739813407993857?t=oJkjAj8U304UEClSUscudQ&s=19

Move snapshots to plugin

3

Not everyone uses snapshots but the current implementation comes with many dependencies so it makes sense to extract it to a separate plugin. @sz-piotr you're gonna love it :->

All basic matchers should have corresponding validators

2

For example we have: expect.stringMatching(...) but not expect().toBeAStringMatching(...)

* read the whole thing, * add missing examples, * solve todos from sourcecode (ensure some conventions for docs)