posit-dev / posit-dev/positron
R test explorer doesn't surface unhandled warnings well
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
System details:
Positron and OS details:
Positron Version: 2025.07.0 (Universal) build 204
Code - OSS Version: 1.100.3
Commit: 03ae7a5393c776bb24c23d2aa6a6bfbba90cbc5e
Date: 2025-06-30T16:28:59.945Z (3 wks ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Session details:
R 4.5.0
Describe the issue:
Tests only show errors, not warnings in the Positron test pane
Steps to reproduce the issue:
- Create a test that emits a warning
- Use the test keyboard shortcut to run test through the Positron IDE
e.g.
example_function <- function() {
# This function does nothing
warning("This is an example warning from example_function.")
return(NULL)
}
test_that("example_function()", {
expect_null(example_function())
})
Expected or desired behavior:
I would like to see some sort of indication that there are warnings, e.g. a yellow warning icon
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
Reproduce the issue in the Positron test pane using the R example that calls warning() and the test_that() case, then inspect how test results are surfaced. The work is done when an R test warning produces a clear indication, such as a warning icon, alongside the existing test result display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100