REditorSupport / REditorSupport/vscode-R
Unit and integration tests
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
Currently, we only have very limited testing of the features of vscode-R.
We might need to put a demo R package and R script folder in the repo and run tests with opening the folder as a workspace folder and test at least the following features:
- Language server startup
- Session watcher
- R markdown commands
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 by reviewing the repository's existing test setup, then determine where a demo R package and R script folder could support opening a workspace folder. Cover language server startup, the session watcher, and R Markdown commands; done means these features have automated unit or integration coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript, vscode
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100