RubyMine 2017.1.1 EAP: Bug-Fix Update

Hi there,

RubyMine 2017.1.1 EAP (build 171.4073.18) is available to fix a painful regression that prevented running RSpec tests from context in the recently launched RubyMine 2017.1. Now it works just fine.

run rspec rubymine

As for other fixes, the inability to “Select all” that might have affected some users has been fixed. The fonts that lost anti-aliasing in v2017.1 have also become smooth again across all JetBrains IDEs.

If you are listening to our EAP channel, consider updating from the IDE (RubyMine | Check for updates) or downloading this EAP directly from our EAP page on Confluence.

See the release notes for the full list of improvements.

Cheers!

Your RubyMine Team

This entry was posted in Announcement and tagged , . Bookmark the permalink.

12 Responses to RubyMine 2017.1.1 EAP: Bug-Fix Update

  1. James T says:

    This issue seems to be present in 2017.2.4, in cases where a new rspec file is created and NOT added to git. If you add to git upon creation, the context menu option exists to run the rspec script.

  2. Will says:

    I am experiencing this issue yet again in 2018.1.3 as of this week. There needs to be at least some way to set test framework priority beyond apparently just their alphabetical order.

    • Olga Kuvardina says:

      Hello Will! Could you please specify what exactly doesn’t work in your case, I’ve checked and RSpec tests are run as RSpec in 2018.1.3 so probably you have another steps.

  3. Ashley Angell says:

    I am experiencing this with my 2018.2 installation. It is driving me crazy and costing me dearly in efficiency. The running of specs with context works from inside the file view, but when I click. folder from the project view, it will only ever run *_spec.rb’s inside the root of the /spec folder.

    Can anyone help PLEASE?

Leave a Reply

Your email address will not be published. Required fields are marked *