aruba 0.9.0.pre → 0.9.0.pre2

data/features/commands/output/all_output.feature

@@ -0,0 +1,445 @@
+Feature: All output of commands which were executed
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the output should contain" step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Detect subset of one-line output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'hello world'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain "hello world"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect absence of one-line output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'hello world'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should not contain "good-bye"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect subset of multiline output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain:
+        \"\"\"
+        hello
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect absence of subset of multiline output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should not contain:
+        \"\"\"
+        good-bye
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @posix
+  Scenario: Detect exact one-line output for posix commands
+    Given a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `printf 'hello world'`
+        Then the output should contain exactly:
+        \"\"\"
+        hello world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect exact one-line output for ruby commands
+    Given an executable named "bin/cli" with:
+    """ruby
+    #!/usr/bin/env ruby
+
+    print "hello world"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain exactly:
+        \"\"\"
+        hello world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect exact one-line output with ANSI output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "\e[36mhello world\e[0m"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      @keep-ansi-escape-sequences
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain exactly:
+        \"\"\"
+        \e[36mhello world\e[0m
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect exact one-line output with ANSI output stripped by default
+    Given the default aruba exit timeout is 12 seconds
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "\e[36mhello world\e[0m"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain exactly:
+        \"\"\"
+        hello world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect exact multiline output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -ne "hello\nworld"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain exactly:
+        \"\"\"
+        hello
+        world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect subset of one-line output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'hello world'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain "hello world"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect subset of one-line output with regex
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'hello, ruby'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should match /^hello(, world)?/
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect subset of multiline output with regex
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld\nextra line1\nextra line2\nimportant line"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should match:
+        \"\"\"
+        he..o
+        wor.d
+        .*
+        important line
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Negative matching of one-line output with regex
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo "hello, ruby"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should not match /ruby is a better perl$/
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Negative matching of multiline output with regex
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld\nextra line1\nextra line2\nimportant line"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the output should not match:
+        \"\"\"
+        ruby
+        is
+        a
+        .*
+        perl
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match passing exit status and partial output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo "hello world"
+    exit 0
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then it should pass with:
+        \"\"\"
+        hello
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match passing exit status and exact output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -ne "hello\nworld"
+    exit 0
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then it should pass with exactly:
+        \"\"\"
+        hello
+        world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match failing exit status and partial output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    exit 1
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then it should fail with:
+        \"\"\"
+        hello
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+
+  Scenario: Match failing exit status and exact output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    exit 1
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then it should fail with:
+        \"\"\"
+        hello
+        world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match failing exit status and output with regex
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    exit 1
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then it should fail with regex:
+        \"\"\"
+        hello\s*world
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect output from all processes
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'This is cli1'
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'This is cli2'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli1`
+        When I run `cli2`
+        Then the stdout should contain exactly:
+        \"\"\"
+        This is cli1
+        \"\"\"
+        And the stdout should contain exactly:
+        \"\"\"
+        This is cli2
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect output from all processes (deprecated)
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'This is cli1'
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'This is cli2'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli1`
+        When I run `cli2`
+        Then the stdout should contain exactly:
+        \"\"\"
+        This is cli1
+        This is cli2
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/commands/output/stdout.feature

@@ -0,0 +1,66 @@
+Feature: Stdout of commands which were executed
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the output should contain" step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Match output in stdout
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain "hello"
+        Then the stderr should not contain "hello"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match stdout on several lines
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'GET /'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain:
+        \"\"\"
+        GET /
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match output on several lines where stdout contains quotes
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'GET "/"'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain:
+        \"\"\"
+        GET "/"
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass