feat(workbench): cover Workbench Jobs and Background Jobs

[samcofer]

Background

A Posit customer mapped their UAT test plan against VIP and identified Workbench Jobs as a feature with no coverage today. Both Workbench Jobs (run on a separate Kubernetes pod) and Background Jobs (run in the same session) are first-class Workbench features that customers exercise during acceptance — there's nothing deployment-specific about them.

What's missing

src/vip_tests/workbench/ has no test_jobs.feature. The existing tests cover session launch, suspend/resume, and capacity, but never submit a script as a job.

Proposed scenarios

@workbench
Feature: Workbench Jobs and Background Jobs

  Scenario: User can submit a Workbench Job from RStudio Pro
    Given the user is logged in to Workbench
    When the user starts a new RStudio session
    And the user submits a short R script as a Workbench Job
    Then the job reaches Completed state
    And the job log contains the expected output
    And the session is cleaned up

  Scenario: User can submit a Background Job from RStudio Pro
    Given the user is logged in to Workbench
    When the user starts a new RStudio session
    And the user submits a short R script as a Background Job
    Then the Background Jobs pane shows the job as Completed
    And the session is cleaned up

Acceptance criteria

• A new src/vip_tests/workbench/test_jobs.feature with both scenarios, tagged @workbench.
• Step definitions in src/vip_tests/workbench/test_jobs.py that drive the RStudio Workbench Jobs / Background Jobs UI via Playwright.
• A short bundled test R script (e.g. Sys.sleep(2); cat("hello from job\n")) shipped with the test, written into the session's working directory.
• Cleanup: any leftover job artifacts removed.

Notes

• Workbench Jobs use Launcher infrastructure, so this scenario also indirectly verifies the Launcher is functional — a useful side effect.
• This depends on the in-session execution primitive (separate issue) only for writing the script file into the session; otherwise it's standalone.

[posit-vip-triage]

Pull request created: #316

Generated by Triage open issues on posit-dev/vip · ● 3.9M

posit-dev/vip, engine: copilot, version: 1.0.48, model: claude-sonnet-4.5, id: 26656786301, workflow_id: issue-triage, run: https://github.com/posit-dev/vip/actions/runs/26656786301 -->

[posit-vip-triage]

I've created a plan for adding Workbench Jobs and Background Jobs test coverage. The plan proposes two BDD scenarios driven by Playwright that validate both job types through the RStudio Pro UI, with cleanup logic to remove artifacts. See the plan PR for full details on architecture, components, and open questions around UI selectors and timeout configuration.

Generated by Triage open issues on posit-dev/vip for issue #302 · ● 3.9M · ◷

[posit-vip-triage]

🤖 An implementation PR is being prepared for this issue based on the merged plan from #316.

The implementation adds:

• Two new @workbench BDD scenarios in test_jobs.feature: Background Job runs and completes and Workbench Job runs and completes
• Playwright step definitions with graceful pytest.skip guards when the Jobs UI is unavailable in a deployment
• RStudio job pane selectors for both Background Jobs and Workbench Jobs (Launcher) panes
• A configurable job_timeout option in WorkbenchConfig (default 120 s) so operators can tune the wait for slow clusters via [workbench] job_timeout in vip.toml
• Selftests for the new config field

Generated by Implement an approved plan PR for issue #316 · ● 50.3M · ◷