posit-dev / posit-dev/connectapi
Improve test coverage
Open
Nobody has claimed this yet.
good first issue :heart:
help wanted :heart:
- Dominant language
- R
- Stars
- 54
- Forks
- 27
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 1
Description
We're up around 70%. Would love to get closer to 100%!
Some ideas:
- schedule.R
- Particularly "display," which is time sensitive...
- variant.R
- tag_page.R - or deprecate / move to
rscpages - lazy.R
- remote.R (needs LDAP CI... 😬 )
- #156
- content.R
- get_group_permission
- content_delete_group
- content_add_group
- browse.R - is this possible to test non-interactively...?
Contributor guide
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
Start with the unchecked coverage targets in schedule.R, variant.R, lazy.R, remote.R, content.R, and browse.R, using the linked Codecov views where provided. Prioritize the named functions and the schedule.R “display” path, then verify that tests cover the selected behavior and that coverage improves; remote.R may require the LDAP CI noted in #156.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100