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:
https://t.co/6DNfCLnMii
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
Good news everyone! We've replaced Relish with our own self hosted documentation, see: https://t.co/IRRewsawl6 to link through to each libraries examples.
@mhenrixon Thank you for testing this, the drop downs don’t work on mobile safari, will fix!
The https://t.co/tBUHd4k13W link worked from here but the relishapp link is a 404 (which is why we are replacing it) are you seeing a 404 from https://t.co/tBUHd4k13W?
These are somewhat url compatible with the old relish docs so if search takes you to:
https://t.co/5OASppF7r8…
You can change this to:
https://t.co/fT2DNwxrhA…
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) https://t.co/NSoGM7zLBn 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:
https://t.co/Y6k2e7dbmN
You can find the cucumber scenarios and readmes in the repos still and we're looking at alternatives.
@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'
```
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!
Now that we’ve told you about @buildkite Test Analytics, I can start showing you some sneaky screenshots of the product. Am I allowed to do this? I’m not sure…I haven’t actually asked anyone. But it’s Friday afternoon, and I’m pretty sure everyone’s gone home 😎 (1/12) 🧵
@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 😂