Tod Beardsley
1deacad2be
Came up on Twitter, where Justin may have been trolling a little: https://twitter.com/jstnkndy/status/798671298302017536 We have a `print_good` method, but not a `print_bad`, which seems a little weird for Ruby -- opposite methods should be intuitive as Justin is implying. Anyway, I went with alias_method, thanks to the compelling argument at https://github.com/bbatsov/ruby-style-guide#alias-method ...since Metasploit is all about the singleton, and didn't want to risk some unexpected scoping thing. Also dang, we define the `print_` methods like fifty billion times! Really should fix that some day.
11 lines
410 B
Ruby
11 lines
410 B
Ruby
RSpec.shared_examples_for 'Msf::Module::UI::Message' do
|
|
it_should_behave_like 'Msf::Module::UI::Message::Verbose'
|
|
|
|
it { is_expected.to respond_to :print_error }
|
|
it { is_expected.to respond_to :print_bad }
|
|
it { is_expected.to respond_to :print_good }
|
|
it { is_expected.to respond_to :print_prefix }
|
|
it { is_expected.to respond_to :print_status }
|
|
it { is_expected.to respond_to :print_warning }
|
|
end
|