Test your Chai HTTP knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is the purpose of `expect(res).to.be.json` as a Chai HTTP-specific assertion?
Questions in this quiz
What is the purpose of `expect(res).to.be.json` as a Chai HTTP-specific assertion?
Why might a team choose to write Chai HTTP-based integration tests specifically for critical API endpoints, in addition to unit tests for the underlying business logic those endpoints depend on?
How do you send a JSON request body with a POST request using Chai HTTP?
How does Chai HTTP relate to Chai's core `expect`/`should`/`assert` interfaces, given that it's described as a "plugin"?
What does `res.body` typically contain after a Chai HTTP request completes, assuming the server responded with JSON?
What is the basic pattern for making a test request with Chai HTTP against an Express app?
How does Chai HTTP typically handle testing an endpoint expected to return an error status, like a 404 or 400?
What is Chai HTTP?
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?
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)?
How does Chai HTTP typically handle testing an endpoint that requires an `Authorization` header (e.g. a bearer token)?
What is a reasonable comparison between Chai HTTP and SuperTest, given that both are popular Node.js libraries for testing HTTP servers?