RubyMine
 
2024.1
Shortcuts: Windows
Get RubyMine
You are viewing the documentation for an earlier version of RubyMine.
  1. Test
  2. Run tests

Run tests

Last modified: 19 April 2024

Run the selected test or test folder: CtrlShiftF10

Stop the current test session: CtrlF2

Running tests directly in a file or folder

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 CtrlShiftF10. Alternatively, click the gutter icon next to the test class or test method and select Run '<test name>' from the list.

    The gutter icon changes depending on the state of your test:

    • The gutter icon marks a set of tests.

    • The gutter icon marks new tests.

    • The gutter icon marks successful tests.

    • The gutter icon marks failed tests.

    Run a specific test from the editor

  • You can run all tests in one or several files or a folder at once. Select the required folder or test files and press CtrlShiftF10. Alternatively, call the context menu and select Run 'All tests in <directory name>' or Run 'All specs in <directory name>' depending on the testing framework in use.

    Run all tests in a directory

Running tests using the Run widget

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.

  1. Create a new run configuration or save a temporary one.

  2. Use the Run widget on the main toolbar to select the configuration you want to run.

  3. Click or press ShiftF10.

    Running a run/debug configuration for tests

tip

To preserve the tab of a run configuration even if you execute another run configuration, you may pin it.

After RubyMine finishes running your tests, it shows the results in the Run tool window on the tab for that run configuration. For more information about analyzing test results, refer to Explore test results.

Run tests using Rake tasks

To run tests using a Rake task, do the following:

tip

RubyMine automatically creates the Rake run configurations for running the Minitest and RSpec tests in Rails applications - test and spec. Learn how to run code using configurations from Run tests using a predefined configuration.

Run tests after commit

When you want to check that your changes wouldn't break the code before pushing them, you can do that by running tests as commit checks.

note

This feature is only available for Git and Mercurial.

Set up test configuration

  1. Open the Commit tool window as described in the following topics:

  2. Click Show Commit Options the Settings button.

  3. Under the Commit Checks menu, next to the Run Tests option, click Choose configuration and select which configuration you want to run.

    Pre-commit checks menu

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

Stop tests

Rerun tests

Rerun a single test

  • Right-click a test on the tab for the run configuration in the Run tool window and select Run 'test name'.

Rerun all tests in a session

  • Click the Rerun button on the Run toolbar or press CtrlF5 to rerun all tests in a session.

Rerun failed tests

  • Click the Rerun Failed Tests icon on the Run toolbar to rerun only failed tests.

    Hold Shift and click to choose whether you want to Run the failed 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 Rerun Automatically Rerun Automatically on the test results toolbar to enable the autotest-like runner.

    The Rerun Automatically option

Debug failed tests

If you don't know why a test fails, you can debug it.

See also

Reference