2014-03-14 00:31:24 -04:00
|
|
|
require_relative 'helper'
|
2011-12-10 10:09:49 -05:00
|
|
|
|
|
|
|
describe Pry::Hooks do
|
|
|
|
before do
|
|
|
|
Pry::CLI.reset
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "parsing options" do
|
|
|
|
it 'should raise if no options defined' 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::CLI.parse_options(["--nothing"]) }.to raise_error Pry::CLI::NoOptionsError
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
2013-09-05 20:11:29 -04:00
|
|
|
|
|
|
|
it "should remove args from ARGV by default" 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
|
|
|
argv = ['filename', '-v']
|
2013-09-05 20:11:29 -04:00
|
|
|
Pry::CLI.add_options do
|
|
|
|
on :v, "Display the Pry version" do
|
|
|
|
# irrelevant
|
|
|
|
end
|
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
|
|
|
end.parse_options(argv)
|
2015-01-22 13:38:52 -05:00
|
|
|
argv.include?('-v').should eq false
|
2013-09-05 20:11:29 -04:00
|
|
|
end
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
describe "adding options" do
|
|
|
|
it "should be able to add an option" do
|
|
|
|
run = false
|
|
|
|
|
|
|
|
Pry::CLI.add_options do
|
|
|
|
on :optiontest, "A test option" do
|
|
|
|
run = true
|
|
|
|
end
|
|
|
|
end.parse_options(["--optiontest"])
|
|
|
|
|
2015-01-22 13:38:52 -05:00
|
|
|
run.should eq true
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
it "should be able to add multiple options" do
|
|
|
|
run = false
|
|
|
|
run2 = false
|
|
|
|
|
|
|
|
Pry::CLI.add_options do
|
|
|
|
on :optiontest, "A test option" do
|
|
|
|
run = true
|
|
|
|
end
|
|
|
|
end.add_options do
|
|
|
|
on :optiontest2, "Another test option" do
|
|
|
|
run2 = true
|
|
|
|
end
|
|
|
|
end.parse_options(["--optiontest", "--optiontest2"])
|
|
|
|
|
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
|
|
|
run.should equal true
|
|
|
|
run2.should equal true
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "processing options" do
|
|
|
|
it "should be able to process an option" do
|
|
|
|
run = false
|
|
|
|
|
|
|
|
Pry::CLI.add_options do
|
|
|
|
on :optiontest, "A test option"
|
2014-01-11 08:42:25 -05:00
|
|
|
end.add_option_processor do |opts|
|
2011-12-10 10:09:49 -05:00
|
|
|
run = true if opts.present?(:optiontest)
|
|
|
|
end.parse_options(["--optiontest"])
|
|
|
|
|
2015-01-22 13:38:52 -05:00
|
|
|
run.should eq true
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
it "should be able to process multiple options" do
|
|
|
|
run = false
|
|
|
|
run2 = false
|
|
|
|
|
|
|
|
Pry::CLI.add_options do
|
|
|
|
on :optiontest, "A test option"
|
|
|
|
on :optiontest2, "Another test option"
|
2014-01-11 08:42:25 -05:00
|
|
|
end.add_option_processor do |opts|
|
2011-12-10 10:09:49 -05:00
|
|
|
run = true if opts.present?(:optiontest)
|
2014-01-11 08:42:25 -05:00
|
|
|
end.add_option_processor do |opts|
|
2011-12-10 10:09:49 -05:00
|
|
|
run2 = true if opts.present?(:optiontest2)
|
|
|
|
end.parse_options(["--optiontest", "--optiontest2"])
|
|
|
|
|
2015-01-22 13:38:52 -05:00
|
|
|
run.should eq true
|
|
|
|
run2.should eq true
|
2011-12-10 10:09:49 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
end
|
|
|
|
end
|