-
Notifications
You must be signed in to change notification settings - Fork 72
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
Reorganise Ruby tests #375
Conversation
carve out logrus before updating golang please |
.gitignore
Outdated
@@ -17,7 +17,6 @@ bin/ | |||
.vagrant/ | |||
build/ | |||
.bundle/ | |||
.vscode/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we remove this from git ignore?
.vscode/launch.json
Outdated
"program": "rake test TEST=${file}" | ||
} | ||
] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please lets avoid any unnecessary IDE related staff out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I added these only before finding out that adding rake
might make sense, and now ruby-lsp
runs tests just fine. Removing!
@@ -1,6 +1,6 @@ | |||
require "test_helper" | |||
|
|||
class TrivialIntegrationTests < GhostferryTestCase | |||
class TrivialIntegrationTest < GhostferryTestCase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL: ruby-lsp
doesn't recognise test classes with plural names
Re: |
Reorganise to run minitests with
rake
and enable a few neat things:main.rb
ruby-lsp
goodness in Code: run/debug single test and test explorerFWIW I wanted to do the same for golang, but the current Go extension for Code requires
1.19+
, so ago
update may be due in a separate PR. Any objections to do that?