From: Dylan Kuhn <dylan.k.kuhn@gmail.com>
Date: Tue, 28 May 2013 01:56:14 +0000 (-0700)
Subject: Use the STDOUT saving technique so tests can pass.
X-Git-Tag: v0.10.0~28^2~6
X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=fba2f4ee98b2f635ec630430c33bb797fdff64e0;p=wvm%2Fwvm.git

Use the STDOUT saving technique so tests can pass.

The wp aliases in my PATH made me oblivious before...
---

diff --git a/features/search-replace.feature b/features/search-replace.feature
index f18dd363..fa11307e 100644
--- a/features/search-replace.feature
+++ b/features/search-replace.feature
@@ -15,12 +15,31 @@ Feature: Do global search/replace
       guid
       """
 
-  Scenario: Large search/replace
+  Scenario: Small guid search/replace
     Given a WP install
 
+    When I run `wp option get siteurl`
+   
+    And save STDOUT as {SITEURL}
+
+    And I run `wp post generate --count=100`
+
+    And I run `wp search-replace {SITEURL} testreplacement`
+    Then STDOUT should be a table containing rows:
+    """
+    Table	Column	Replacements
+    wp_posts	guid	102
+    """
+  Scenario: Large guid search/replace
+    Given a WP install
+
+    When I run `wp option get siteurl`
+
+    And save STDOUT as {SITEURL}
+
     And I run `wp post generate --count=1200`
 
-    And I run `wp search-replace $( wp option get siteurl ) testreplacement`
+    And I run `wp search-replace {SITEURL} testreplacement`
     Then STDOUT should be a table containing rows:
     """
     Table	Column	Replacements