[DRE-commits] [ruby-aruba] 64/74: Moved tests

Hideki Yamane henrich at moszumanska.debian.org
Sat Nov 28 01:16:46 UTC 2015


This is an automated email from the git hooks/post-receive script.

henrich pushed a commit to branch debian/sid
in repository ruby-aruba.

commit 312f66132e67c531265f16e42f6cad6392c66f54
Author: Dennis Günnewig <dg1 at ratiodata.de>
Date:   Fri Nov 27 09:29:01 2015 +0100

    Moved tests
---
 features/output.feature               | 41 -----------------------------------
 features/steps/command/stdout.feature |  2 +-
 2 files changed, 1 insertion(+), 42 deletions(-)

diff --git a/features/output.feature b/features/output.feature
deleted file mode 100644
index 666d2a1..0000000
--- a/features/output.feature
+++ /dev/null
@@ -1,41 +0,0 @@
-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 stdout from named source
-    When I run `printf 'hello'`
-    And I run `printf 'goodbye'`
-    Then the stdout from "printf 'hello'" should contain "hello"
-    And the stdout from "printf 'hello'" should contain exactly "hello"
-    And the stdout from "printf 'hello'" should contain exactly:
-      """
-      hello
-      """
-    And the stderr from "printf 'hello'" should not contain "hello"
-    And the stdout from "printf 'goodbye'" should not contain "hello"
-
-  Scenario: Detect stderr from named source
-    When I run `bash -c 'printf hello >&2'`
-    And I run `printf goodbye`
-    Then the stderr from "bash -c 'printf hello >&2'" should contain "hello"
-    And the stderr from "bash -c 'printf hello >&2'" should contain exactly "hello"
-    And the stderr from "bash -c 'printf hello >&2'" should contain exactly:
-      """
-      hello
-      """
-    And the stdout from "bash -c 'printf hello >&2'" should not contain "hello"
-    And the stderr from "printf goodbye" should not contain "hello"
-
-  Scenario: Detect second output from named source with custom name
-    When I set the environment variable "ARUBA_TEST_VAR" to "first"
-    And I run `bash -c 'printf $ARUBA_TEST_VAR'`
-    Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "first"
-    When I set the environment variable "ARUBA_TEST_VAR" to "second"
-    And I run `bash -c 'printf $ARUBA_TEST_VAR'`
-    Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "second"
diff --git a/features/steps/command/stdout.feature b/features/steps/command/stdout.feature
index a34865f..318932a 100644
--- a/features/steps/command/stdout.feature
+++ b/features/steps/command/stdout.feature
@@ -87,7 +87,7 @@ Feature: STDOUT of commands which were executed
     When I run `cucumber`
     Then the features should all pass
 
-  Scenario: 
+  Scenario: Detect stdout from named source
     Given a file named "features/output.feature" with:
     """
     Feature: Run command

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/ruby-aruba.git



More information about the Pkg-ruby-extras-commits mailing list