Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing tests report only the first failing assertion #1

Open
bogdanbranescu opened this issue Aug 26, 2019 · 0 comments
Open

Failing tests report only the first failing assertion #1

bogdanbranescu opened this issue Aug 26, 2019 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@bogdanbranescu
Copy link
Contributor

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:
    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:
     AssertionError: expected header X-First-Bad-Header with value undefined to match this_header_enjoys_espresso
@bogdanbranescu bogdanbranescu added the bug Something isn't working label Aug 26, 2019
@catalin-me catalin-me self-assigned this Sep 11, 2019
@atrifan atrifan added this to To do in Chakram - functional engine via automation Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants