Run tests
Quick way
If your tests don't require any specific actions before start and you don't want to configure additional options, such as code coverage, you can run them by using the following options:
Place the caret at the test class to run all tests in that class, or at the test method, and press Ctrl+Shift+F10. Alternatively, click the gutter icon next to the test class or test method.
The gutter icon changes depending on the state of your test:
The
gutter icon marks new tests.
The
gutter icon marks successful tests.
The
gutter icon marks failed tests.
You can run all tests in one or several files or a folder at once. Select the required folder or test files and press Ctrl+Shift+F10. Alternatively, call the context menu and select testing framework in use.
or depending on the
Customizable way
When you run a test, RubyMine creates a temporary run configuration. You can save temporary run configurations, change their settings (for example, pass task arguments, specify environment variables, and so on) , share them with other members of your team.
Create a new run configuration or save a temporary one.
From the list on the main toolbar, select the configuration you want to run.
Click
or press Shift+F10.
After RubyMine finishes running your tests, it shows the results in the Run tool window on the Test Runner tab. For more information on how to analyze test results, refer to Explore test results.
Run tests using Rake tasks
To run tests using a Rake task, do the following:
From the main menu, select
Ctrl+Alt+R.In the invoked popup, start typing the name of a Rake task that runs tests, for example,
rake test
orrake spec:controllers
.Select the desired Rake task from the list and press Enter.
Run tests before commit
When you want to check that your changes wouldn't break the code before committing them, you can do that by running tests as a pre-commit check.
Set up test configuration
After you have set up the test configuration, the specified tests will run every time you make a commit.
![Non-modal commit dialog running a test Non-modal commit dialog running a test](https://resources.jetbrains.com/help/img/idea/2021.3/rm_run_tests_before_commit_1.png)
Stop tests
Use the following options on the Run toolbar of the Test Runner tab:
Click
or press Ctrl+F2 to terminate the process immediately.
![Stop running tests Stop running tests](https://resources.jetbrains.com/help/img/idea/2021.3/rm_stop_running_tests.png)
Rerun tests
Rerun a single test
Right-click a test on the Test Runner tab of the Run tool window and select Run 'test name'.
Rerun all tests in a session
Click
on the Run toolbar or press Ctrl+F5 to rerun all tests in a session.
Rerun failed tests
Click
on the Run toolbar to rerun only failed tests.
Hold Shift and click
to choose whether you want to Run the tests again or Debug them.
Rerun tests automatically
In RubyMine, you can enable the autotest-like runner: any test in the current run configuration restarts automatically after you change the related source code.
Click
Toggle auto-test on the Run toolbar to enable the autotest-like runner.
Debug failed tests
If you don't know why a test fails, you can debug it.
In the editor, click the gutter on the line where you want to set a breakpoint.
There are different types of breakpoints that you can use depending on where you want to suspend the program. For more information, refer to Breakpoints.
Right-click the
gutter icon next to the failed test and select Debug 'test name'.
The test that has failed will be rerun in the debug mode. After that, the test will be suspended, allowing you to examine its current state.
You can step through the test to analyze its execution in detail.