112 Followers
0 Following
10 Posts
RSpec - BDD for Ruby
Websitehttps://rspec.info
Githubhttps://github.com/rspec

Announcing the Monorepo.

We’re switching to a monorepo out of the rspec/rspec repository on Github. The main branch is a combination of all the repos main branches, dev is rebased on this during the transition phase with the intent of main becoming the default when this is complete.

Please switch any git dependencies to at least main if not dev on that repo, for the full story:

https://rspec.info/blog/2024/11/introducing-the-monorepo/

Introducing the RSpec monorepo, and some updates on the future of RSpec.

Announcing the Monorepo.

We’re switching to a monorepo out of the rspec/rspec repository on Github. The main branch is a combination of all the repos main branches, dev is rebased on this during the transition phase with the intent of main becoming the default when this is complete.

Please switch any git dependencies to at least main if not dev on that repo, for the full story:

https://rspec.info/blog/2024/11/introducing-the-monorepo/

Introducing the RSpec monorepo, and some updates on the future of RSpec.

Sneak preview for ruby.social ahead of the blog post... RSpec is moving to a monorepo...
https://github.com/rspec/rspec
Comparing rspec-mocks-v3.13.3...rspec-mocks-v3.13.4 · rspec/rspec

The RSpec monorepo. Contribute to rspec/rspec development by creating an account on GitHub.

GitHub

Hey Foss-to-verse, does anyone have a hint for a “view HTML output" in a Github action?

I'm building middleman pages for the RSpec website in GHA and they have a handy action source for me to create "deploy on merge" for the docs [so awesome compared to what we've been doing] but I'd like to add a "preview enviroment" to the PR phase.

@zenspider It shows no values here because you've provided a custom failure message, you could include the values here if you wanted to, but the purpose of this feature is hide overly complicated diffs where it would be confusing and instead show a simpler message.

Also please use less ableist language in examples, e.g:

```
RSpec.describe “is so frustrating!" do
specify "how frustrating is it?” do
a, b = 1, 2
expect(a). to eq(b), “Not very but #{a} is not eq #{b}”
end
end
```

Hi everybody! We've just released `rspec-rails` 6.1.0 with some enhancements and fixes for Rails 7.1! 🎉

Per our versioning scheme this 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 should be safe for all.

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://github.com/rspec/rspec-rails/blob/main/Changelog.md

#ruby #rspec #rails

rspec-rails/Changelog.md at main · rspec/rspec-rails

RSpec for Rails 5+. Contribute to rspec/rspec-rails development by creating an account on GitHub.

GitHub
Anyone have any ideas why using `fork` inside an Rspec example might cause Rspec when it gets to the end of the run? Specifically when a JS feature spec (i.e. one that will also fork its own process) gets executed after the forking example. It looks like the Chrome processes launched by ferrum/cuprite are not being exited. I've tried calling `exit!` in the forked processes to avoid the registered `at_exit` firing prematurely but that doesn't seem to help.
With rubydoc.info having issues recently this is a good time to remind everyone that alongside our newly self-hosted gherkin documentation, we also host our own rdoc at https://rspec.info/documentation/ e.g. https://rspec.info/documentation/3.12/rspec-core/
RSpec documentation

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

These are somewhat url compatible with the old relish docs so if search takes you to:

https://relishapp.com/rspec/rspec-expectations/docs/compound-expectations

You can change this to:

https://rspec.info/features/3-12/rspec-expectations/compound-expectations/

And get the same page.

Feedback welcome!

RSpec documentation

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://write.as/mattwynne/relish

You can find the cucumber scenarios and readmes in the repos still and we're looking at alternatives.

Relish

Back in 2010, David Chelimsky was re-writing RSpec, and had the idea to use Cucumber scenarios to drive the development. The RSpec websit...

Matt Wynne