test(workbench): add RStudio Git-pane commit/push scenario (validated against live Workbench)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
Context
PR #363 (Git operations from Workbench sessions, closes #306) originally included a "Commit and push using the RStudio Git pane" scenario plus a RStudioGitPane page object. It was dropped before merge because:
- The selectors in
RStudioGitPanewere never validated against a live Workbench instance (the code carried a TODO note to that effect). - The working-directory setup used
Rscript -e 'setwd(...)'run in the terminal, which spawns a separate R process and does not change the already-running RStudio session's working directory — so the Git pane would never discover the cloned repo.
The terminal-based Git scenarios (RStudio/VSCode/Positron clone + branch/commit/push) shipped in #363 and work.
What's needed
- Re-add the RStudio Git-pane GUI scenario, with selectors verified against a live Workbench (e.g. ganso01-staging).
- Set the session working directory via
rstudio_eval(page, 'setwd(...)')(in-session), not a terminalRscriptsubprocess. - Re-introduce a validated
RStudioGitPanepage object.
References
- PR #363
- Original feature issue #306
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
Start with the terminal-based Git scenarios from PR #363, the dropped RStudioGitPane page object, and the rstudio_eval entry point. Validate the RStudio Git-pane selectors against the referenced live Workbench, set the working directory in-session, and finish when the GUI commit/push scenario runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100