87d0fa46f8
Get rid of RSpec implicit block expectation syntax
...
The syntax was removed in rspec-expectations 3.8.5.
Related:
https://blog.rubystyle.guide/rspec/2019/07/17/rspec-implicit-block-syntax.html
https://github.com/rspec/rspec-expectations/pull/1125
https://github.com/rubocop-hq/rspec-style-guide/issues/76
This is a follow-up to #12397 and unpins `rspec-expectations`.
2019-10-04 23:12:34 +03:00
8f3f2f74b4
Move shared example from pro into framework
...
MS-1361
2016-04-07 13:09:52 -05:00
f5415c8058
Move pro concern logic into framework
...
MS-1361
2016-04-07 10:59:40 -05:00
3b0170e87d
Import workspace IP validation from Mdm
...
This allows us to actually test the validations, since the code calls
out to Rex::Socket::RangeWalker.
MS-902
2016-03-29 17:56:22 -05:00
d6bf0fd781
decribe -> RSpec.describe
...
MSP-13484
Disabled expose_dsl_globally in spec_helper, so need to qualify
top-level describe.
2015-12-10 21:47:22 -06:00
1fa26e2afb
cleans up a bunch of spec msftidy issues
2014-08-26 15:24:08 -05:00
b5351eec2b
adding .to_credential
...
Metasploit::Framework::Credential and Metasploit::Credential::Core
need to be consumable by the login scanners. the easiest way to do this
was to create a shared to_credential method on both that return Metasploit::Framework::Credential
MSP-9912
2014-06-26 11:05:59 -05:00
Phil Pirozhkov