Implement API integration tests between items and outfits endpoints

[rak3rman]

Description

In smoke tests and in unit tests for items and outfits, we never test the functionality of how the items and outfits API route directly interact with each other through the database. Write a few non-exhaustive tests in hono/tests/integration/items-outfits.integration.test.ts that checks for these interactions. For example, create an item (POST /api/items) and assign to an outfit (POST /api/items). Then get the outfit (GET /api/outfit) and ensure that item details are contained within the outfit object. Another good example would be to validate the cascading delete on DELETE /api/items. When this route is invoked, all outfits associated to this item should also be deleted. Write tests until you feel as if you've tested all obvious edges.

Acceptance Criteria

Generated by Zenhub AI

• [ ] Scenario: Create an item and assign it to an outfit
  • Given a new item is created through a POST request to /api/items
  • When an outfit is created through a POST request to /api/outfits and the item is assigned to it
  • Then the outfit object, when retrieved through a GET request to /api/outfit, should contain the item details
  • [ ] Scenario: Delete an item and cascading delete of associated outfits
  • Given an item is created through a POST request to /api/items and assigned to an outfit through a POST request to /api/outfits
  • When the item is deleted through a DELETE request to /api/items
  • Then all outfits associated with the deleted item should also be deleted, and a GET request to /api/outfits should not return the deleted outfit
  • [ ] Scenario: Retrieve outfit details with associated items
  • Given an outfit is created through a POST request to /api/outfits and items are assigned to it through a POST request to /api/outfits
  • When the outfit is retrieved through a GET request to /api/outfit
  • Then the outfit object should contain the details of all associated items