-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the current scope
available for stubbing everywhere
#310
Comments
Indeed. I'd like to be able to express a spec along the lines of: it 'should be deprecated' do
scope.expects(:warning).with('... is deprecated.')
...
end |
+1 |
@DavidS any progress on this by any chance? :-) |
This is - sadly - still a side^3 project for me. |
Any chance of this getting addressed anytime soon? |
@smu-ggl my comment from last year still applies. Sadly. The most I can currently invest is reviewing code. |
@rodjek looks like this was briefly added to a milestone, but then removed. Any update on this? |
Resurrecting the thread! Here's how I'm doing it currently: let(:pre_condition) do
# Mask `warning` for testing
<<~PRE_CONDITION
function warning($message) { notify { 'warning_test': message => $message } }
PRE_CONDITION
end
it { is_expected.to create_notify('warning_test').with_message(/<whatever>/) } |
From the discussion in #108: it is necessary to have access to the compiling
scope
in all example groups, as in d3f737eThe text was updated successfully, but these errors were encountered: