Conversation
Code Coverage SummaryDiff against mainResults for commit: 29aca26 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 31 suites 40s ⏱️ Results for commit 29aca26. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 21637a6 ♻️ This comment has been updated with latest results. |
|
Funny that locally it had better coverage... I will continue here to reach 80% |
osenan
left a comment
There was a problem hiding this comment.
Good job!
I've checked the coverage report and we achieved the goal. Thanks to the changes the code seems better. I liked the tests, they are very helpful to understand the functions tested.
I put comments on the way we process the html table output to generate a data.frame. I think having too many function calls within the same line is not optimal for interpreting the code. That is why I recommend to put every action with a pipe and if the pipe is repeated to create a helper function.
Increate test coverage to 80%.
During testing I've found some redundant code which could be optimized.