Feat/cypress refactor

[rsteckline]

What kind of change does this PR introduce?

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor(DRY-ing up/ reorganizing code, etc.)
• Small fix (Corrected a typo, removed a comment, etc.)

Issue/feature/bug description:

• Refactor the tests to align with new API response structure
• Refactor the error handling
• Implement working tests

Checklist before requesting a review

• I ran the code locally and verified that there are no visible errors.
• I have performed a self-review of my code
• I have refactored my code before this push
• The commit message follows our guidelines
• My code follows the code style of this project.

What’s next:

Finalize styling!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
laboulangerie	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2024 10:58pm

[dsstevens]

We combined some small CSS tweaks with the styling branch and for the sake of time also put code cleanup on here as well. We were working sync and tag-teamed this work so happy with the results.