skeleton code for unit tests complete #15
Merged
Conversation
This file contains 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
TheSirLancelot
requested review from
nevermore23274,
Rey41888,
oavf15 and
tyoung-99
nevermore23274
approved these changes
Oct 24, 2023
|
Did you run the tests? Edit: In the current state, they should all pass for all three browsers. |
|
Going to merge this to main so I can test the new workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Links #8
Skeleton is there. We just need to go through each feature and define what they look like. Once we do that we should be able to go back through the unit test functions and set the functionality we are testing (obv it will fail for now, that's how test-driven development works 👍 )