Add a row-count assertion after a many-to-one join in an R analysis script You know the join should not change row count, but the script only relies on memory. Two weeks later, the source system changes and the dashboard is wrong before anyone notices. In tests/testthat/test-data-gates.R, I will add one expectation for [specific assumption] before I trust [specific output]. Review this commitment in 3 days against the actual script, report, or pull request. Add a uniqueness test for IDs before a dashboard summary Add an allowed-values check for a categorical field used in case_when() Add a nonnegative numeric check before…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in