Create Test Cases for Archive Feature in the Desktop Application

[BaloneyBoy97]

Original Issue #139

Description
As a developer,
I need to create comprehensive test cases for the newly implemented archive feature,
So that I can ensure its reliability, functionality, and compatibility with other parts of the application.

Tasks

• Write unit tests to verify that the archive function removes notes from the frontend.
  • Test for successful archive of a note.
  • Test that the confirmation prompt appears before archive.
  • Test that the frontend properly reflects the archive (e.g., note disappears).
• Write unit tests to verify that the archive function works correctly in the backend.
  • Test that the media file is archived from the database.
  • Test that associated annotations are also archived.
• Write integration tests to ensure proper interaction between the frontend and backend during archive.
  • Test the complete flow from triggering the archive button to removing the note and annotations.
  • Test that the UI remains consistent after a note is archived.
• Ensure that tests are regression-free.
• Committed tests should not interfere with other tests or features.

Acceptance Criteria

• At least one unit test and one integration test are created for the archive feature.
  • Unit test verifies proper archive behavior in both frontend and backend.
  • Integration test covers the end-to-end archive process.
• Code is well-commented.
• Commit only the changes that you’ve made.
• All tests pass before merging.
• Tests should run without any errors or timeouts.
• Tests ensure that no residual data remains in the frontend or backend after archive.

This issue ensures the robustness and stability of the delete feature by covering various testing scenarios.

This issue complete last item on the MVP of the project.