Skip to content
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

Add information on what analysts should be testing #209

Open
sarahcollyer opened this issue Nov 14, 2024 · 0 comments
Open

Add information on what analysts should be testing #209

sarahcollyer opened this issue Nov 14, 2024 · 0 comments
Assignees
Milestone

Comments

@sarahcollyer
Copy link
Contributor

We should add a paragraph/some bullet points covering what analysts should be testing, in general terms, and what they shouldn't need to test.

e.g. analysts should take a risk based approach to testing.

  1. don't test everything e.g. safe to assume basic mathematics implementations will work
  2. don't need to test functions from other packages (as long as they are appropriately tested)

Good example is rounding in R - no need to test the actual function in terms of its maths, but you do need to test in the context of your analysis to confirm it's doing what you think it is.

Could present this in an idea lightbulb box like in Quarto

@sarahcollyer sarahcollyer added this to the 2024.2 milestone Nov 14, 2024
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

2 participants