Module: TestLauncher

Defined in:

lib/test_launcher/rubymine.rb,
lib/test_launcher/cli.rb,
lib/test_launcher/search.rb,
lib/test_launcher/queries.rb,
lib/test_launcher/version.rb,
lib/test_launcher/search/ag.rb,
lib/test_launcher/base_error.rb,
lib/test_launcher/search/git.rb,
lib/test_launcher/cli/options.rb,
lib/test_launcher/cli/request.rb,
lib/test_launcher/shell/color.rb,
lib/test_launcher/shell/runner.rb,
lib/test_launcher/frameworks/base.rb,
lib/test_launcher/cli/input_parser.rb,
lib/test_launcher/frameworks/rspec.rb,
lib/test_launcher/rubymine/request.rb,
lib/test_launcher/rubymine/launcher.rb,
lib/test_launcher/frameworks/ex_unit.rb,
lib/test_launcher/frameworks/generic.rb,
lib/test_launcher/frameworks/mochajs.rb,
lib/test_launcher/frameworks/minitest.rb,
lib/test_launcher/shell/history_runner.rb,
lib/test_launcher/frameworks/implementation/test_case.rb

Overview

To allow us to simply specify our run configuration as:

-r test_launcher/rubymine

we need to put the currently executing script in with the args.

Consider the following examples:

ruby -r test_launcher/rubymine /path/to/test.rb

vs

ruby -r test_launcher/rubymine spring testunit /path/to/test.rb

In one case, our test to run is $0 and in another case it’s an ARGV. So we throw them in the same bucket and let the launcher figure it out. It doesn’t matter since we will ‘exec` a new command anyway.

Defined Under Namespace

Modules: CLI, Frameworks, Queries, Rubymine, Search, Shell Classes: BaseError

Constant Summary

VERSION =

"2.21.0"