rspec
Here are 1,080 public repositories matching this topic...
-
Updated
Nov 6, 2020 - Ruby
-
Updated
Oct 24, 2019 - Ruby
-
Updated
Nov 5, 2020 - Ruby
-
Updated
Apr 2, 2020 - Ruby
-
Updated
Feb 20, 2020
I really like enforcing one expectation per example. But with RSpec's exception matching, you need two expect calls if you want to assert something about an exception:
expect { my_code }.to raise_error(MyErrorType) do |error|
expect(error.message).to match /something went wrong/
end
There's no way to match against the error message without first wrapping the call, and RSpec o
-
Updated
Feb 29, 2020 - Ruby
-
Updated
Mar 9, 2020 - Ruby
-
Updated
Nov 1, 2020 - Ruby
-
Updated
Nov 7, 2020 - Ruby
-
Updated
Oct 13, 2020 - Ruby
-
Updated
Oct 30, 2020 - Ruby
-
Updated
Aug 26, 2020 - Ruby
-
Updated
Jan 16, 2019 - Ruby
-
Updated
Jun 8, 2018 - Ruby
-
Updated
Oct 5, 2018 - Ruby
Improve this page
Add a description, image, and links to the rspec topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the rspec topic, visit your repo's landing page and select "manage topics."


Summary
The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a