Remove front end unit tests from code and README.md #371
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.
As mentioned in #211, packages/jupyter-ai/README.md says "Frontend tests. This extension is using Jest for JavaScript code testing." but there are no meaningful Jest tests. We also don't plan to implement JS unit tests, plan to cover our needs with snapshot-based E2E testing.
This PR removes front end unit tests from code and README.md. This will remove confusion and create correct expectations. If need would arise, adding js unit tests back would be trivial.