-
Notifications
You must be signed in to change notification settings - Fork 19
[Tests] Unit tests for Angular parts #164
Copy link
Copy link
Open
Labels
code componentRelated to the CSSSCode Component libraryRelated to the CSSSCode Component librarydocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededmainRelated to the main siteRelated to the main site
Metadata
Metadata
Assignees
Labels
code componentRelated to the CSSSCode Component libraryRelated to the CSSSCode Component librarydocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededmainRelated to the main siteRelated to the main site
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.tsfile, which defines what tests to run on the Angular building block.Additional context
https://angular.dev/guide/testing
https://jasmine.github.io/
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
CSSS Code