-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug rspec test with bundle exec #410
Comments
Did you put a breakpoint to somewhere you want to stop? |
Yes, and without |
Thank you. Can you share 'rdbg' information in "OUTPUT" tab? |
Sure, here you go:
Then there's the error I mentioned in the issue description:
The output shows the file name twice in the {
"type": "rdbg",
"name": "RSpec current line with rdbg",
"useBundler": false,
"command": "bundle exec rspec",
"request": "launch",
"script": "${file}:${lineNumber}",
"args": []
} But I get the same error, and the following output:
|
I can confirm this issue. "name": "Debug Rspec with current file",
"type": "rdbg",
"request": "launch",
"command": "rspec",
"script": "${file}",
"useBundler": true,
"args": [] |
Good point, I hadn't realized the issue is with RSpec+bundle generally, I thought it was associated with running a specific spec line. I'm changing the issue title. |
Have you tried This is my current setup which works for me. |
That is odd, this fails for me with |
This tipped me off from the README:
The config that works for me is then
|
This did not work for me, but it got me in the right track. I generated the RSpec binstub with {
"type": "rdbg",
"name": "RSpec current line with rdbg",
"request": "launch",
"useBundler": true,
"script": "./bin/rspec",
"args": [
"${file}:${lineNumber}"
],
}, |
I'm able to run Rspec on a given line with the following
rdbg
call:I could also make it work within VSCode if I don't use bundler, by using the following launch.json::
However, if I change
command
tobundle exec rspec
, I get the following message without much clarification:Is there a way to do it currently? Otherwise, let me know if I should push a PR to make this possible.
The text was updated successfully, but these errors were encountered: