test(workbench): session tests leave created files (Untitled*.ipynb) behind after cleanup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
What happens: The Workbench session-cleanup fixture quits/removes the session, but files created inside a session during a test — most visibly JupyterLab Untitled*.ipynb notebooks from test_launch_jupyter / test_jupyterlab_extensions — remain in the test account's home directory. Over many runs these accumulate (16+ observed on a live deployment).
Why it matters: Test litter accrues in the shared test account, and stale leftover notebooks can pop dialogs (e.g. a lingering "Error Starting Kernel" modal) that intercept clicks in later runs — a latent source of flakiness.
Scope: Non-destructive cleanup of VIP-created files at session/test teardown (tag or track what the test creates and remove only that; must never touch pre-existing user content). Distinct from session cleanup (#467), which is about quitting sessions, not deleting files.
Not a blocker for #484 — surfaced during its live validation.
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
Locate the Workbench session-cleanup fixture and inspect test_launch_jupyter and test_jupyterlab_extensions, where the leftover files are created. First trace how session teardown currently works and how VIP-created files could be identified without including pre-existing content. Done means teardown removes only files created during the test and the affected tests no longer leave Untitled*.ipynb files behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100