Created
October 22, 2018 09:17
-
-
Save ZiiSolutions/0bdf61531c7cc6c79a3ba5e99d5fe640 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@collection | |
@capi | |
Feature: Content API Collection Order | |
Background: | |
Given I have a Content API subscription | |
Scenario: User can see Content API collection items in the same order as in Content Repository | |
Given I have entitlement to see the "news" schedule in the Content API | |
And I have 20 items prefixed by "story" with profile "story" and type "text" for the service "paservice:news" | |
And I ingest the items via the Content Pipeline's item receiver endpoint | |
And I have the "news" schedule | |
And I add the items to the "news" schedule | |
When I ingest the "news" schedule via the Content Pipeline's collection receiver endpoint | |
And the "news" schedule has been indexed | |
And all items have been indexed | |
And I should be able to lookup the "news" schedule in the Content Repository | |
When I list all the items in the "news" collection in Content API with a limit of 5 | |
Then the Content API items are ordered in the same order as the "news" schedule in Content Repository | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment