Sha256: 5c69936b058259cc798446f95629095a4bcca55a6b549e532f5b8ec120617435
Contents?: true
Size: 1023 Bytes
Versions: 5
Compression:
Stored size: 1023 Bytes
Contents
Feature: Get path to command
Sometimes you only know a commands name, but not where to find it. Here comes
`which` to the rescue.
Background:
Given I use a fixture named "cli-app"
Scenario: Existing executable
Given an executable named "bin/aruba-test-cli" with:
"""bash
#!/bin/bash
exit 0
"""
And a file named "spec/which_spec.rb" with:
"""ruby
require 'spec_helper'
RSpec.describe 'Find path for command', :type => :aruba do
it { expect(which('aruba-test-cli')).to match %r{tmp/aruba/cli-app/bin/aruba-test-cli} }
end
"""
When I run `rspec`
Then the specs should all pass
Scenario: Non-existing executable
Given a file named "bin/aruba-test-cli" does not exist
And a file named "spec/which_spec.rb" with:
"""ruby
require 'spec_helper'
RSpec.describe 'Find path for command', :type => :aruba do
it { expect(which('aruba-test-cli')).to be_nil }
end
"""
When I run `rspec`
Then the specs should all pass
Version data entries
5 entries across 5 versions & 1 rubygems