RSpec - BDD for Ruby

Announcing the Monorepo. We’re switching to a monorepo out of the rspec/rspec repository on Github, for the full story: rspec.info/blog/2024/11/i…

Rails 6.0.4 contains some of these bug fixes for your convenience [but does not officially support 7.1] and is the last 6.0.x release. For all the changes see: github.com/rspec/rspec-ra…

Hi! We've just released `rspec-rails` 6.1.0 with some enhancements and fixes for Rails 7.1! 🎉 As per `rspec-rails` versioning this release supports Rails 6.1, 7.0, and 7.1 and is now our maintained release stream, it contains no breaking changes [that we know of] so good to go!

@sudhindraRao You probably need to access via https, I think twitter just added http by default, it’s GitHub pages underneath so has a let’s encrypt cert

Great easier to find url. Shows as `Not Secure` for me though.

@RogersKonnor @mhenrixon @Benoit_Tgt We’ve fixed the drop-down, probably will ship some more mobile layout tweaks later

Good news everyone! We've replaced Relish with our own self hosted documentation, see: rspec.info/documentation/ to link through to each libraries examples.

@mhenrixon We’ve fixed the drop-down, probably will ship some more mobile layout tweaks later

@rspec Not working for me. Get a 404 on the link below and on mobile safari I can’t click on anything to open the actual docs.

@mhenrixon Thank you for testing this, the drop downs don’t work on mobile safari, will fix! The rspec.info link worked from here but the relishapp link is a 404 (which is why we are replacing it) are you seeing a 404 from rspec.info?

These are somewhat url compatible with the old relish docs so if search takes you to: relishapp.com/rspec/rspec-ex…… You can change this to: rspec.info/features/3-12/…… And get the same page. Feedback welcome!

Hey everyone still here, if you feel like you need a non bird site place to follow RSpec, we also have an account on (at rspec at) ruby.social please follow us there also as its easier to update with apps (we're Ivory fans).

Hi everyone, we know RelishApp is down, its unfortunately out of our hands to do anything about it, see Matt's post for some context: write.as/mattwynne/reli… You can find the cucumber scenarios and readmes in the repos still and we're looking at alternatives.

@GhostBrain The logo can be considered CC NC SA if that helps, I’ll update the repo at some point soon.

@rspec Hi there! Is RSpec logo under the MIT license? I can't find logo in rspec-core repo, but found in github.com/rspec/rspec.gi… repo that is not declare its license.

@GhostBrain That’s a good question…

@fbeausoleil You can create aliases in your shell itself.,e.g. I have in my `~/.profile`: ``` alias rr='git ls-files -mo --exclude-standard | exists | grep _spec\.rb$ | xargs bundle exec rspec' alias ro='bundler exec rspec --only-failures' alias rn='bundler exec rspec --next-failure' ```

Using @rspec, I sometimes need to re-run failing specs. `--only-failures` is a GREAT feature, but I'd love to have an alias for `--failures-only`, as that's how I suck at remembering the correct option name.

Is your test suite slow on CI? Take a sneaky peek at how @buildkite founder @keithpitt made some of his RSpec tests faster using their new Test Analytics!

@onghu @PCurell @ruby_rails_bot # RecordFileOutput.run(:global, "") # running exe # => 2021-08-18 08:27:00.866983 +0100 # RecordFileOutput.run(:global, "") # => 2021-08-18 08:27:00.866983 +0100 # RecordFileOutput.run(:specific, "") # running exe # => 2021-08-18 08:27:07.200896 +0100

@PCurell @ruby_rails_bot @rspec Thanks for the answers - let me look at shared examples maybe

Hi, @rspec folk! I'm using #RSpec to prep inputs, run an EXE (takes 2 min) & then run assertions on output files. The assertions have ~10 contexts with 20 examples each. How can I split these into diff files so that I run the EXE once only. Hints/ links appreciated. #ruby

@onghu @PCurell @ruby_rails_bot e.g. module RecordFileOutput module_function def run(name, config) @outputs ||= {} @outputs[name] || @outputs[name] = call_exec(config) end def call_exec(config) puts "running exe" Time.now end end

@onghu @PCurell @ruby_rails_bot If you isolate the code into a module function thats memoised, you can call it safely at any point and it would only run once, to allow different config to run you could then use “names” to distinguish different memoised outputs.

@knowuh @V8 No it’s the standard Ruby `did_you_mean` suggestion caused by a `NameError` and you happen to.. er.. have a to_v8 method defined somewhere. Did you put `expect(…).to_have(…)` when you meant `expect(…).to have(..)` somewhere?

@realntl @waiting_for_dev @_solnic_ @tom_dalling Also, and I’ll add this disclaimer, I love seeing new testing frameworks trying new things, just because RSpec does something one way doesn’t mean I’m not a fan of other ways. I also use ExUnit a lot and I could do a whole series of tweets on a comparison with RSpec 😂

@rspec @waiting_for_dev @_solnic_ @tom_dalling With TestBench, sharing local variables across contexts is a judgment call of the tester. In general, TestBench doesn't include any features designed to encourage good test design, but it does deliberately lack features designed to cope with problematic tests.

IMHO @rspec 's `let` blocks are misused 99% of the time. Tests are about doing expectations for how code behaves on different scenarios, so you can't extract shared context so happily. On top of that, tests are also documentation, so you want to minimize indirection.