The-Strategy-Unit / The-Strategy-Unit/data_science
Tests / test-driven development
Open
Nobody has claimed this yet.
session: C&C ☕
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
- What is a unit test?
- Writing good unit tests - How to write them, when to write them, how many is enough
- Testing in the software engineering sense and testing in the data analysis sense
- An example of the former would be checking for data types or logical inconsistencies
- An example of the latter would be checking that a database of adults doesn’t have anyone under 18 in it
- Syntax
- I see and use testthat, but have heard of others like assertr
- There seems to be new recommendations beyond testhat::test_that()
- Is there a function called it() now? How do I do that properly?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or documentation entry point is named. Review the repository structure and existing learning materials first, then decide where this broad testing guide belongs; done means the listed unit-testing, data-analysis testing, and R syntax topics are covered coherently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100