[Tests] Unit tests for Angular parts #164
Description
Motivation behind the feature and what it will do
Writing unit tests is something you'll probably end up doing if you ever go into a software development role. Most people hate writing them (I know I do), but if you want to actually make yourself stick out then learn how to unit test early. Angular ships with the Jasmine testing framework, so we'll just utilize that.
Which part of the application will this feature be for?
The main site and component library.
Code changes
Every Angular component, service, etc. should have a *.spec.ts file, which defines what tests to run on the Angular building block.
Additional context
https://angular.dev/guide/testing
https://jasmine.github.io/
- This issue will never be resolved unless we somehow run out of tests to write
- We could use a wiki entry to explain how to write unit tests
- Unit tests get kinda weird when asynchronous behaviour needs to be tested, but Angular 20 simplified it
- Karma (the test runner) has been deprecated, so we might need to move onto Jest later on
Needs test
Instead of making an issue for each, just mention if you write unit tests for something and we can cross it out.
Main site
- components/nav-bar
- components/tab-bar
- pages/affiliates
- pages/committees
- pages/common-room
- pages/events
- pages/home
- pages/officers
- pages/readme
- services/application
- services/gsap
CSSS Code
- article
- button
- card
- menu
- tabs