enhancement: add {test_name} variable to use with --name option about atom-ruby-test HOT 7 OPEN

@roychoo: Did your PR cover tests with spaces? I used to write my tests like this:

test "awesome feature" do
  ...
end

I the settings I changed the single test command to ruby -I test {relative_path} -n /{regex}/ but this did not trigger my test. I think minitest only recognise valid ruby method names in the regex. It would be great if spaces get replaced by underscore. If I run the test on the console with ruby -I test /path/to/test.rb -n /awesome_feature/ the test run.

from atom-ruby-test.

so i found a fork of the m gem which works with minitest-5, and was able to use that as a work around for this:

add this to your Gemfile:

group :test do
  gem 'm', git: 'https://github.com/ANorwell/m.git', :branch => 'minitest_5'
end

and use this for your run configuration:

bundle exec m /path/to/project/{relative_path}:{line_number}

would still prefer to have a {test_name_at_line} variable, but this gets me thru...

from atom-ruby-test.

Thanks @tony-kerz, the fork of the m gem works well.

from atom-ruby-test.

hey @GerritWanderer glad that works for you.

the other option i recently stumbled across is using zeus which can run a test at the cursor as well.

check out the section on zeus in this document: http://brendankemp.com/essays/atom-is-ready-to-be-your-editor/

i have trended to this solution as i have never used zeus before and it is also pretty cool in terms of eliminating start up wait times for a ruby process. check it out here: https://github.com/burke/zeus

regards,
tony.

from atom-ruby-test.

I'll try Zeus out. This is an great article by Brendan Kemp, I already discovered some new features :)

from atom-ruby-test.

I had made a pr #49 to run test based on regex.

from atom-ruby-test.

For those landing on this issue like me, I made a Pull Request attempt (#117) for the annoying limitation mentioned above by @roychoo

from atom-ruby-test.