Server unit tests

🎯 Goal / Objective

A clear and concise description of what this task aims to achieve. Why is this task important?

There are no automated tests for our server in boneset-api/server.js. Currently, our only way of validating the server's functionality is by manually running the site, and this can easily miss critical features.

✅ Tasks to be Completed

A checklist of the specific, actionable steps required to complete this issue. This helps track progress.

• Set up supertest as a dev dependency in package.json
• Set up a tests/server.test.js file. It should have the following imports:

  import express from "express"
  import request from "supertest"
  

• Write tests for each API endpoint. Test that calling the endpoints correctly return expected status and information, that failures return the expected status code, and any potential edge cases.
• Correct any failing tests.

See sub-issues for more details.

Acceptance Criteria

A checklist of conditions that must be met for this task to be considered complete. How will we verify that it's done correctly?

• Existing endpoints are well covered.
• The new feature is implemented as described.
• All related code passes the repository's workflow checks (linting, tests).
• The application runs without errors after the changes are made.

Additional Context

Add any other context, notes, screenshots, or links that might be helpful for completing this task.

See this file in another repository for an example of the kind of workflow we want. That will give you a quick idea of how to test the endpoints.

Start by reading boneset-api/server.js to inventory the existing endpoints, then inspect package.json and the repository workflow checks. Set up tests/server.test.js with the requested imports and use the endpoint behavior to define success, failure, and edge-case assertions. Done means the endpoints are covered, tests and linting pass, and the application still runs without errors.