Skip to content

Instantly share code, notes, and snippets.

@limhoff-r7
Created April 25, 2013 14:38
Show Gist options
  • Save limhoff-r7/5460202 to your computer and use it in GitHub Desktop.
Save limhoff-r7/5460202 to your computer and use it in GitHub Desktop.
RSpec 3 deprecation warnings
WARNING: subject accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/post/meterpreter/packet_spec.rb:455:in `block (3 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:47:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:21:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:33:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:8:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:9:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
WARNING: let declaration `client_request` accessed in a `before(:all)` hook at:
/Users/luke.imhoff/git/limhoff-r7/metasploit-framework/spec/lib/rex/proto/http/client_request_spec.rb:10:in `block (2 levels) in <top (required)>'
This is deprecated behavior that will not be supported in RSpec 3.
`let` and `subject` declarations are not intended to be called
in a `before(:all)` hook, as they exist to define state that
is reset between each example, while `before(:all)` exists to
define state that is shared across examples in an example group.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment