chore(CI): prepare JEST CI verification job integration in G-A for client SPA app #51
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
I fully agree with that! Thank you for this update, @bougwal ! |
falberthen
approved these changes
May 31, 2024
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.
Hey @falberthen - I hope you are well! A Friday evening PR, as per our last discussion yesterday- Let me know what you think about running the client app unit tests with jest in the pipeline - As we add more unit tests in the future, the business logic should be very well covered - Still as discussed, the UI part can be addressed too with either extended jest DOM tests or one of the available options (cypress or playwright) in the future.