Sha256: 81dfe697331a7094e2d77ff1423de66f4b2b554415424dd410d8203ed4fc4313

Contents?: true

Size: 1.26 KB

Versions: 10

Compression:

Stored size: 1.26 KB

Contents

Feature: Access STDOUT of command

  You may need to `#stop_all_commands` before accessing `#stdout` of a single
  command - e.g. `#last_command_started`.

  Background:
    Given I use a fixture named "cli-app"
    And the default aruba io wait timeout is 1 seconds

  Scenario: Existing executable
    Given an executable named "bin/cli" with:
    """bash
    #!/bin/bash
    echo 'Hello, Aruba!'
    """
    And a file named "spec/run_spec.rb" with:
    """ruby
    require 'spec_helper'

    RSpec.describe 'Run command', :type => :aruba do
      before(:each) { run('cli') }
      before(:each) { stop_all_commands }
      it { expect(last_command_started.stdout).to start_with  'Hello' }
    end
    """
    When I run `rspec`
    Then the specs should all pass

  Scenario: Waiting for output to "appear" after 2 seconds
    Given an executable named "bin/cli" with:
    """bash
    #!/bin/bash
    sleep 1
    echo 'Hello, Aruba'
    """
    And a file named "spec/run_spec.rb" with:
    """ruby
    require 'spec_helper'

    RSpec.describe 'Run command', :type => :aruba, :io_wait_timeout => 2 do
      before(:each) { run('cli') }
      it { expect(last_command_started.stdout).to start_with 'Hello' }
    end
    """
    When I run `rspec`
    Then the specs should all pass

Version data entries

10 entries across 10 versions & 2 rubygems

Version Path
aruba-0.14.7 features/api/command/stdout.feature
aruba-0.14.6 features/api/command/stdout.feature
aruba-0.14.5 features/api/command/stdout.feature
aruba-0.14.4 features/api/command/stdout.feature
aruba-0.14.3 features/api/command/stdout.feature
aruba-win-fix-0.14.2 features/api/command/stdout.feature
aruba-0.14.2 features/api/command/stdout.feature
aruba-0.14.1 features/api/command/stdout.feature
aruba-0.14.0 features/api/command/stdout.feature
aruba-0.13.0 features/api/command/stdout.feature