-
Notifications
You must be signed in to change notification settings - Fork 212
Unit test coverage #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
UPDATE: Will be addressed in this F2F: http://www.topcoder.com/challenge-details/30057203/?type=develop |
UPDATE: Unit test coverage was as high as 83% of branches, 93% of functions, 93% of lines and 93% of statements, but it droped low again after migration of challenge listing code into this repo. |
ThomasKranitsas
pushed a commit
that referenced
this issue
Jul 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the last challenge there are some failing tests, also the global test coverage should be increased.
From that submission comments
The time for that component comes from a call to Topcoder API. That call should be mocked with standard Jest methods, and then snapshot test will be feasible.
The text was updated successfully, but these errors were encountered: