2019-05-02 18:33:56 -04:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
2012-09-15 17:50:15 -04:00
|
|
|
describe "exit-program" do
|
|
|
|
|
it 'should raise SystemExit' do
|
Switch test suite to RSpec
Removes Bacon and Mocha
Reasoning explained in this comment: https://github.com/pry/pry/issues/277#issuecomment-51708712
Mostly this went smoothly. There were a few errors that I fixed along
the way, e.g. tests that were failing but for various reasons still
passed. Should have documented them, but didn't think about it until
very near the end. But generaly, I remember 2 reasons this would happen:
`lambda { raise "omg" }.should.raise(RuntimeError, /not-omg/)` will pass
because the second argument is ignored by Bacon. And `1.should == 2`
will return false instead of raising an error when it is not in an it
block (e.g. if stuck in a describe block, that would just return false)
The only one that I felt unsure about was spec/helpers/table_spec.rb
`Pry::Helpers.tablify_or_one_line('head', %w(ing)).should == 'head: ing'`
This is wrong, but was not failing because it was in a describe block
instead of an it block. In reality, it returns `"head: ing\n"`,
I updated the test to reflect this, though I don't know for sure
this is the right thing to do
This will fail on master until https://github.com/pry/pry/pull/1281 is merged.
This makes https://github.com/pry/pry/pull/1278 unnecessary.
2014-08-10 18:26:47 -04:00
|
|
|
expect { pry_eval('exit-program') }.to raise_error SystemExit
|
2012-09-15 17:50:15 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
|
|
it 'should exit the program with the provided value' do
|
|
|
|
|
begin
|
|
|
|
|
pry_eval 'exit-program 66'
|
|
|
|
|
rescue SystemExit => e
|
2015-03-10 16:49:29 -04:00
|
|
|
expect(e.status).to eq(66)
|
2012-09-15 17:50:15 -04:00
|
|
|
else
|
|
|
|
|
raise "Failed to raise SystemExit"
|
|
|
|
|
end
|
|
|
|
|
end
|
|
|
|
|
end
|