All Test Cases

#### Use Jest Testing Suite
Thorough testing through snapshots as well as state management based on actions performed

###### General Overview
- [ ] Create at least one test case for every component
- [ ] State management checks to review objects based on manipulating actions
- [ ] Tests check various buttons & pages
- [ ] Ensure all tests are passed by the current version of the application
- [ ] Make sure to create a snapshot for each component

###### Detailed Overview
The following are linked issues to test the various different functionalities that exist in our application at a granular level
- [ ] Authentication & Workshop Login #69
- [ ] Data Downloads #70
- [ ] Create workshop #71
- [ ] Read workshop #72
- [ ] Update workshop #73
- [ ] Delete workshop & Erasing student progress #74
- [ ] User mark progress
- [ ] Admin graphs
- [ ] Level enabled access
- [ ] Different pages & Navbar

Start by finding the existing Jest test setup and any current test folder to identify how tests are organized. Use the issue’s linked functional areas as the scope (auth/workshop login, data downloads, create/read/update/delete workshop, admin graphs, etc.) and map each to the relevant component or page. Add snapshot tests and action/state tests for those parts, then run the project’s Jest test command to validate the suite. Done looks like all listed areas covered by tests and the full Jest suite passing.

索引モデルが issue の本文から書いたものです。