Skip to content

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

Closed
birdofpreyru opened this issue Apr 10, 2017 · 3 comments
Closed

Unit test coverage #6

birdofpreyru opened this issue Apr 10, 2017 · 3 comments

Comments

@birdofpreyru
Copy link
Collaborator

After the last challenge there are some failing tests, also the global test coverage should be increased.

From that submission comments

SubmissionManagement component will fail the snapshot test since we need to dinamically show the user the time left till the current phase ends.

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.

@birdofpreyru
Copy link
Collaborator Author

UPDATE: Will be addressed in this F2F: http://www.topcoder.com/challenge-details/30057203/?type=develop

@birdofpreyru
Copy link
Collaborator Author

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.

@ajefts ajefts closed this as completed May 30, 2017
@cwdcwd
Copy link
Contributor

cwdcwd commented Mar 1, 2018

test coverage

sushilshinde pushed a commit that referenced this issue Feb 8, 2019
sushilshinde pushed a commit that referenced this issue Jul 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants