Test your Chai HTTP knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is the significance of Chai HTTP supporting both a Promise-based (`.then()`) and (in some versions/configurations) a callback-based style for handling the response of a test request?
In this round
What is the significance of Chai HTTP supporting both a Promise-based (`.then()`) and (in some versions/configurations) a callback-based style for handling the response of a test request?
How can you assert on the response body's content using Chai HTTP, beyond just the status code?
What is the basic pattern for making a test request with Chai HTTP against an Express app?
What is the purpose of testing an Express application via actual HTTP requests (as Chai HTTP enables) rather than only unit-testing individual route handler functions by calling them directly with mocked request/response objects?
How does Chai HTTP relate to Chai's core `expect`/`should`/`assert` interfaces, given that it's described as a "plugin"?
What is Chai HTTP?
What is the underlying HTTP client library that Chai HTTP is commonly understood to build on top of, and what does this relationship suggest about Chai HTTP's own design?
What is the purpose of `expect(res).to.redirect` (or checking `res.redirects`) as a Chai HTTP assertion related to HTTP redirects?
How does Chai HTTP typically handle testing an endpoint that requires an `Authorization` header (e.g. a bearer token)?
What is a reasonable use case for `.field()` and `.attach()` methods in Chai HTTP (mirroring similar functionality in the underlying superagent library it builds on)?
What is the purpose of `expect(res).to.be.json` as a Chai HTTP-specific assertion?
What does the `.to.have.status(200)` assertion provide, as a Chai HTTP-specific addition to Chai's core assertion vocabulary?