summaryrefslogtreecommitdiff
path: root/features/api
diff options
context:
space:
mode:
authorBryan McLellan <btm@opscode.com>2012-04-13 14:52:56 -0700
committerBryan McLellan <btm@opscode.com>2012-04-13 14:52:56 -0700
commitebf48a8ead34b0e00bd023feb03151ee10187ff1 (patch)
treebedaa45ed91fbb5d1669b0f416b66f5339084cce /features/api
parent55abbd779fe9751e8a8bfd66ef5a03d2ce0aa06d (diff)
downloadchef-ebf48a8ead34b0e00bd023feb03151ee10187ff1.tar.gz
feature test fixes: search result ordering isn't garunteed
Diffstat (limited to 'features/api')
-rw-r--r--features/api/search/show_search.feature3
1 files changed, 1 insertions, 2 deletions
diff --git a/features/api/search/show_search.feature b/features/api/search/show_search.feature
index 665d6b5bca..656b63e8b2 100644
--- a/features/api/search/show_search.feature
+++ b/features/api/search/show_search.feature
@@ -128,8 +128,7 @@ Feature: Search data via the REST API
And the search index has been committed
When I authenticate as 'bobo'
And I 'GET' the path '/search/client?q=*:*'
- Then the inflated responses key 'rows' item '0' should be a kind of 'Chef::ApiClient'
- And the inflated responses key 'rows' item '0' should respond to 'name' with 'isis'
+ Then a 'Chef::ApiClient' with item name 'isis' should be in the search result
Scenario: Search for a type of object that does not exist
Given I am an administrator