RSpec: Efficiently rerunning failed examples during development

Note

Don't use reruns as a mean to work around flaky tests. You should always try to fix those instead of rerunning them regularly.

Setup

Configure RSpec to persist the result of your test runs to a file. This is necessary to be able to rerun examples.
Add this to your spec/spec_helper.rb :

  config.example_status_persistence_file_path = 'spec/examples.txt'

Rerun all failed examples using `--only-failures`

bundle exec rspec --only-failures (or g rs --only-failures with geordi) will rerun all examples which failed in the last run.

Rerun a single failed example using `--next-failure`

bundle exec rspec --next-failure (or g rs --next-failure with geordi) will rerun only the first previously failed example.
Once you fixed this spec and it´s green again the next run of g rs --next-failure will run the next failed example. This will continue until all specs are green and can be very useful if you just implemented your new feature and now need to fix all the specs it broke.

rspec.info

Martin Schaflitzl

Say thanks3

Last edit

7 months ago

Julian

License

Source code in this card is licensed under the MIT License.

How to fix: WrongScopeError when using rspec_rails with Rails 6.1

tl;dr: Upgrade the gem to at least 4.0.1

When you use rspec_rails in a version < 4 with Rails 6.1 you may encounter an error like this:

Failure/Error:
  raise WrongScopeError,
    "`#{name}` is not available from within an example (e.g. an ...

RSpec: Tagging examples and example groups

In RSpec you can tag examples or example groups with any tags you like simply by saying

describe ReportCreator, slow: true do
  # ..
end

describe ReportCreator do
  it 'generates reports', slow: true do
    # ...
  end
end

You can ...

Run your own code before specific RSpec examples

You probably know about the possibility to tag scenarios in Cucumber to run your own piece of code before the actual scenario is run which looks like that:

@foo
Scenario: Do something
...

and you place the following snippet into ...

Output the descriptions of RSpec examples while they are running

In order to

track down warnings and to see failing specs immediately
or to get an overview of the core functionalities,

you can use RSpec's "nested" format. It looks like this:

Tool
  validations
    should require model to be ...

Posted by Martin Schaflitzl to makandra dev (2023-10-09 08:04)

RSpec: Efficiently rerunning failed examples during development

Note

Setup

Rerun all failed examples using --only-failures

Rerun a single failed example using --next-failure

Related cards:

Rerun all failed examples using `--only-failures`

Rerun a single failed example using `--next-failure`