Repository navigation
[9/N] Add unit tests for AlgorithmNotFound404 component - #100
Merged
luciankt merged 9 commits intoOct 12, 2026
Conversation
This was referenced Oct 3, 2026
Merged
This was referenced Oct 3, 2026
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
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.
🥞 Stack
Addresses #93
Context
Adds unit test coverage for
AlgorithmNotFound404.jsto ensure 404 messaging, return navigation link, and layout components render reliably when an unknown algorithm route is requested.Changes Made
src/components/__tests__/AlgorithmNotFound404.test.jsto unit testAlgorithmNotFound404.Test Plan
npm test -- --watchAll=falsenpm run lintandnpx prettier --check src/