So, for this task, we'll be using Github, cause they have notes and we currently don't 😞
What's this task about?
We want to add unit tests to our new and existing endpoints to both test the new changes and endpoints I added, and to make manual testing easier when we make the changes on the frontend, also for resiliency going forward. We should be able to trust our endpoints, and if a change is causing an undesired effect, we should catch it quickly in the dev phase before shipping it to production.
Implementation Strategy
We currently have 9 soon to be active endpoints:
- user
- sprint
- system
- collaborationRequest
- client
- collaborators
- organization
- board
- task
You can find them here
I ( @Damilope ) will take the first five, and Adegoke ( @Ademyth ) will take the rest. This is also a lot of work, so pace yourself while working through it, you don't want to get burnout. Also, considering you ( @Ademyth ) don't know Typescript yet, I think this is going to be a good introduction to Typescript for you, which means you may see a lot of errors and Typescript may scream at you a bit, but you'll get used to it, and you'll learn a thing or two along the way.
For ( @Ademyth )
Use createOrganization test file as a sample and use it to write the rest. Try to study the code first, and also study the createOrganization endpoint itself, to get a feel for what the test does, and if you have any questions, do let me know. Once you get a solid grasp of it, then you can start writing the tests.
So,
- Clone the repo
- Create a different branch
- Write some tests
- Occasionally push your changes so that I can review them, and give you tips or help where you need it
Happy coding!!
So, for this task, we'll be using Github, cause they have notes and we currently don't 😞
What's this task about?
We want to add unit tests to our new and existing endpoints to both test the new changes and endpoints I added, and to make manual testing easier when we make the changes on the frontend, also for resiliency going forward. We should be able to trust our endpoints, and if a change is causing an undesired effect, we should catch it quickly in the dev phase before shipping it to production.
Implementation Strategy
We currently have 9 soon to be active endpoints:
You can find them here
I ( @Damilope ) will take the first five, and Adegoke ( @Ademyth ) will take the rest. This is also a lot of work, so pace yourself while working through it, you don't want to get burnout. Also, considering you ( @Ademyth ) don't know Typescript yet, I think this is going to be a good introduction to Typescript for you, which means you may see a lot of errors and Typescript may scream at you a bit, but you'll get used to it, and you'll learn a thing or two along the way.
For ( @Ademyth )
Use createOrganization test file as a sample and use it to write the rest. Try to study the code first, and also study the createOrganization endpoint itself, to get a feel for what the test does, and if you have any questions, do let me know. Once you get a solid grasp of it, then you can start writing the tests.
So,
Happy coding!!