-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix tibble snapshots #878
Fix tibble snapshots #878
Conversation
Code Coverage Summary
Diff against main
Results for commit: 7a2eaf4 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
valname label levelcombo exargs | ||
1 AnyGrade Any Grade (%) 1, 2, 3, 4, 5 NULL | ||
2 Grade34 Grade 3-4 (%) 3, 4 NULL | ||
3 Grade5 Grade 5 (%) 5 NULL | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
testthat::expect_true(all(result$WGRHIFL == "Y" & result$GRADDR == "High")) | ||
testthat::expect_identical(nrow(result), 600L) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well solved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm! Thanks Emily for this. I was just wondering how you selected tibbles to make them data.frame and do you think is it worth it to go the extra mile and add tests for col types? (imo not but maybe..)
I made all of the tibbles into data.frames except 2 which I chose to replace with other tests because they were huge tables and the function being tested was supposed to convert all values in the affected columns to the same value so it was much easier to just check that. |
Converted most snapshot
tibble
s todata.frame
s. Replaced 2 unnecessarytibble
snapshots with different tests.Closes #866