`expect_no_error()` loses traceback

Open Beginner friendly
#2,334 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
testing

Research direction

Start at the expect_no_error() entry point and reproduce the failure shown from test-dbplyr.R:57. Check how the simpleError is reported and preserve the traceback in the failure output; done when the example's error includes a useful traceback without losing the existing message.

Written by the indexing model from the issue text.

Description

e.g.

Failure ([test-dbplyr.R:57:3](vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html#)): joins, semi_joins, and set ops work
Expected `dplyr::collect(dplyr::semi_join(db1, db2, by = "x"))` not to throw any errors.
Actually got a <simpleError> with message:
  no applicable method for 'table_path_components' applied to an object of class "c('Pool', 'R6')"

Having the traceback is very useful.

Dominant language
R
Stars
939
Forks
346
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from r-lib/testthat

All issues in r-lib/testthat

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.