Failing tests report only the first failing assertion
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
In order to understand the state of a failing test, a list of all the failing assertions should be provided. See an example of faulty reporting below:
* test file:
```... then: >
expect(response).to.have.header("pragma", "no-cache"),
expect(response).to.have.header("accept-ranges", "bytes"),
expect(response).to.have.header("X-First-Bad-Header", "this_header_enjoys_espresso"),
expect(response).to.have.header("X-Second-Bad-Header", "this_value_drinks_only_decaf")
```
* output:
``` 2) Framework validation playground [vundefined]:
AssertionError: expected header X-First-Bad-Header with value undefined to match this_header_enjoys_espresso
```
Contributor guide
Assessment
This issue has not been assessed yet.