summaryrefslogtreecommitdiff
path: root/features/api/search/show_search.feature
diff options
context:
space:
mode:
authorNuo Yan <nuo@opscode.com>2011-03-10 11:07:42 -0800
committerNuo Yan <nuo@opscode.com>2011-03-10 11:07:42 -0800
commit68b2e2e38bb94fc79af2e606ed77f9d89a2c23b3 (patch)
tree2c4a1df28710af208dab68e746220436f2a2f829 /features/api/search/show_search.feature
parentbab33da3c614effe6dd16764cb12c1a10e653465 (diff)
downloadchef-68b2e2e38bb94fc79af2e606ed77f9d89a2c23b3.tar.gz
Fix wrong ticket number in the tests.
Diffstat (limited to 'features/api/search/show_search.feature')
-rw-r--r--features/api/search/show_search.feature8
1 files changed, 4 insertions, 4 deletions
diff --git a/features/api/search/show_search.feature b/features/api/search/show_search.feature
index 351f5cd82d..717677e140 100644
--- a/features/api/search/show_search.feature
+++ b/features/api/search/show_search.feature
@@ -37,7 +37,7 @@ Feature: Search data via the REST API
@oss_only
Scenario: Search for objects with a manual ascending sort order
- Given PL-450 is resolved in favor of not removing this feature
+ Given PL-540 is resolved in favor of not removing this feature
Given I am an administrator
And a 'data_bag' named 'users' exists
And a 'data_bag_item' named 'francis' exists
@@ -54,7 +54,7 @@ Feature: Search data via the REST API
@oss_only
Scenario: Search for objects with a manual descending sort order
- Given PL-450 is resolved in favor of not removing this feature
+ Given PL-540 is resolved in favor of not removing this feature
Given I am an administrator
And a 'data_bag' named 'users' exists
And a 'data_bag_item' named 'francis' exists
@@ -71,7 +71,7 @@ Feature: Search data via the REST API
@oss_only
Scenario: Search for objects and page through the results
- Given PL-450 is resolved in favor of not removing this feature
+ Given PL-540 is resolved in favor of not removing this feature
Given I am an administrator
And a 'data_bag' named 'users' exists
And a 'data_bag_item' named 'francis' exists
@@ -121,7 +121,7 @@ Feature: Search data via the REST API
And I 'GET' the path '/search/environment?q=name:cucumber'
Then the inflated responses key 'rows' item '0' should be a kind of 'Chef::Environment'
- Scenario: Search for a type of object that does not exist
+ Scenario: Search for a type of object that does not exist
Given I am an administrator
When I authenticate as 'bobo'
And I 'GET' the path '/search/funkensteins'