Update MemoriesController and MemoryTest for CRUD functionality

[FaerieAI]

Summary of changes:

• Updated MemoriesController.php to include CRUD operations for the Memory model.
• Added tests for each CRUD operation in MemoryTest.php.

Changes:

• Added use App\Models\Memory; to import the Memory model.
• Updated index() method to return all Memory objects instead of just one.
• Updated store() method to use the create() method instead of manually creating a new Memory object.
• Updated show() method to use findOrFail() instead of find() to handle cases where the Memory object does not exist.
• Updated update() method to use findOrFail() and update() methods to handle updating an existing Memory object.
• Updated destroy() method to use findOrFail() and delete() methods to handle deleting an existing Memory object.
• Added use RefreshDatabase; and use WithFaker; to import necessary traits for testing.
• Updated it_can_get_all_memories() test to use assertJson() to check if the response matches the expected Memory objects.
• Updated it_can_create_a_memory() test to use assertJson() to check if the response matches the created Memory object and assertDatabaseHas() to check if the Memory object was saved to the database.
• Updated it_can_get_a_single_memory() test to use assertJson() to check if the response matches the expected Memory object.
• Updated it_can_update_a_memory() test to use assertJson() to check if the response matches the updated Memory object and assertDatabaseHas() to check if the Memory object was updated in the database.
• Updated it_can_delete_a_memory() test to use assertDatabaseMissing() to check if the Memory object was deleted from the database.

For additional context, here were my instructions:

---

A description of your next task is:
Alright, let's detail the steps required for step 1.2 in which we set up the CRUD operations and the associated tests.

Step 1.2 Implement CRUD Operations

For MemoriesController:

1. Define the MemoriesController in app/Http/Controllers/MemoriesController.php with methods index, store, show, update, and destroy for handling appropriate CRUD operations.

2. For each method, write the necessary logic. Typically, index will fetch all memory objects, store will save a new object, show will retrieve an object based on id, update will modify existing memory object by its id, and destroy will delete a memory object.

3. Return relevant responses from each method. For instance, return the created memory object in response to store or the memory object after updating it in update.

For routes:

1. After setting up MemoriesController, go to routes/api.php and define routes for every CRUD operation.

2. Use appropriate HTTP methods for each route, for example, GET for index and show, POST for store, PUT/PATCH for update, and DELETE for destroy.

Writing Tests for CRUD operations

In tests/Feature/MemoryTest.php:

1. Write test cases for each of the five methods (index, store, show, update, destroy) of MemoriesController.

2. These cases should generate a request (or a series of requests in some cases) simulating all possible inputs, then examine the response to confirm that it matches the expected behavior.

3. Make sure to write additional cases to cover edge scenarios such as requests containing invalid data or attempts to access non-existent memory objects.

Final Note

Remember, when defining routes and writing tests, keep in mind the REST standard and our API design to maintain consistency. With these steps completed, you should have functioning CRUD operations for the Memory model with matching Pest tests ready to go. It's crucial to run all tests after implementation to ensure everything works as expected.

[github-actions]

❌ Tests failed to complete successfully.

[github-actions]

❌ Tests failed to complete successfully.