test(integration): verify response content-types across HTTP routes

[Ferryx349]

Fixes - #533

[changeset-bot]

🦋 Changeset detected

Latest commit: 0c4da6e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
nostream	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coveralls]

coverage: 65.941% (+0.8%) from 65.108% — Ferryx349:m3 into cameri:main

[Copilot]

Pull request overview

Adds a new Cucumber integration feature to verify that key HTTP endpoints return the expected Content-Type (and status codes), addressing Issue #533’s request to validate response types across routes.

Changes:

• Add a new integration feature (response-types) that exercises several GET/POST HTTP routes and asserts status + Content-Type.
• Add step definitions to issue HTTP requests for the new feature.
• Add a changeset entry for the test addition.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
test/integration/features/response-types/response-types.feature.ts	Adds Cucumber step definitions to make HTTP requests (GET/POST) and store the response in the World state.
test/integration/features/response-types/response-types.feature	Adds scenario outlines covering core GET/POST routes and expected Content-Type values.
.changeset/response-types-integration-tests.md	Adds a changeset entry documenting the new integration coverage.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[cameri]

Some of these tests are calling endpoints that are disabled, so the tests should likely enable the feature before making the HTTP call so you don't just get a 4xx response.

[Ferryx349]

Some of these tests are calling endpoints that are disabled, so the tests should likely enable the feature before making the HTTP call so you don't just get a 4xx response.

Fixed it, please review