Tod Beardsley 1deacad2be Add a print_bad alias for print_error ... 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.		2016-11-15 19:20:42 -06:00
..
matchers	it { should_not -> it { is_expected.not_to	2015-12-10 21:47:22 -06:00
shared	Add a print_bad alias for print_error	2016-11-15 19:20:42 -06:00