Ntu api unit tests#61
Merged
Merged
Conversation
…o ntu_api_unit_tests
… through the use of testing helper function for common response types
… a testingFactor function to test multiple functions at the same time and then also changed the api doc.html such that it no longer flags accessibility issues by allowing users to have keyboard input in order to navigate the document
|
morganthegirlboss
approved these changes
May 17, 2026
nsmzoneli
approved these changes
May 17, 2026
Contributor
nsmzoneli
left a comment
nsmzoneli
left a comment
There was a problem hiding this comment.
Unit tests look fine. no necessary changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Added all the api testing code as well as the api/cognito information doc, will serve as a baseline for api TDD
Related issue
progress?
How to test
assuming in main director:
"cd backend", and then
"npm test" and that should run all tests, at the moment though, it will be all fails until the API routes are completed