sshingler-jkl 0.0.4 → 0.0.5
Sign up to get free protection for your applications and to get access to all the features.
- data/features/calais.feature +38 -0
- data/features/homepage.feature +20 -0
- data/features/http.feature +25 -0
- data/features/mocks/bbc_story.html +2863 -0
- data/features/mocks/calais.json +2464 -0
- data/features/mocks/topix_rss.xml +47 -0
- data/features/mocks/twitter.json +11 -0
- data/features/persistence.feature +10 -0
- data/features/processing.feature +16 -0
- data/features/sanitize-text.feature +47 -0
- data/features/step_definitions/calais_steps.rb +44 -0
- data/features/step_definitions/home_page_steps.rb +20 -0
- data/features/step_definitions/http_steps.rb +49 -0
- data/features/step_definitions/persistence_steps.rb +19 -0
- data/features/step_definitions/processing_steps.rb +30 -0
- data/features/step_definitions/require_steps.rb +14 -0
- data/features/step_definitions/sanitize-text_steps.rb +20 -0
- data/features/step_definitions/twitter_steps.rb +17 -0
- data/features/support/env.rb +36 -0
- data/features/twitter.feature +16 -0
- data/lib/jkl.rb +1 -0
- metadata +21 -1
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
Feature: Calais-Specific features
|
|
2
|
+
In order to use the Calais Meta-Tagging Service
|
|
3
|
+
As a developer
|
|
4
|
+
I want to make some requests and inspect some responses
|
|
5
|
+
|
|
6
|
+
@connection_needed
|
|
7
|
+
Scenario: Post some very simple text to calais, inspect the response
|
|
8
|
+
Given I have some simple text
|
|
9
|
+
When I post to calais
|
|
10
|
+
Then I should get a response
|
|
11
|
+
And I should receive some tags
|
|
12
|
+
|
|
13
|
+
@connection_needed
|
|
14
|
+
Scenario: Post a mock story to calais, inspect the response
|
|
15
|
+
Given I have a sanitized sample BBC story
|
|
16
|
+
When I post to calais
|
|
17
|
+
Then I should get a response
|
|
18
|
+
And I should receive some tags
|
|
19
|
+
|
|
20
|
+
Scenario: Clean up blank items from a calais response
|
|
21
|
+
Given I have a mock calais response
|
|
22
|
+
When I remove the unwanted items
|
|
23
|
+
Then I should receive some tags
|
|
24
|
+
And there should no longer be any "instances"
|
|
25
|
+
And there should no longer be any "relevance"
|
|
26
|
+
And there should no longer be any "blank"
|
|
27
|
+
And there should no longer be any "not_available"
|
|
28
|
+
|
|
29
|
+
Scenario: Go through the calais response tags in a bit more detail
|
|
30
|
+
Given I have a mock calais response
|
|
31
|
+
When I remove the unwanted items
|
|
32
|
+
Then I should receive some tags
|
|
33
|
+
And there should be some "Organization" tags
|
|
34
|
+
|
|
35
|
+
Scenario: Go through the calais response tags as a single array
|
|
36
|
+
Given I have a mock calais response
|
|
37
|
+
Then I should be able to see the whole lot of tags as one block
|
|
38
|
+
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
Feature: Homepage
|
|
2
|
+
In order to use the app
|
|
3
|
+
As a user
|
|
4
|
+
I want to hit the homepage and see some initial trends
|
|
5
|
+
|
|
6
|
+
@connection_needed @acceptance
|
|
7
|
+
Scenario: hit the homepage and view the top 10 trends
|
|
8
|
+
When I surf to '/'
|
|
9
|
+
Then I should see a list of 10 trends
|
|
10
|
+
|
|
11
|
+
@connection_needed @acceptance
|
|
12
|
+
Scenario: add my own trend
|
|
13
|
+
When I surf to '/'
|
|
14
|
+
Given I add my own trend
|
|
15
|
+
|
|
16
|
+
@acceptance
|
|
17
|
+
Scenario: use a mock calais response to layout the page
|
|
18
|
+
When I surf to "/mock"
|
|
19
|
+
Then I should see some stuff
|
|
20
|
+
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
Feature: http features
|
|
2
|
+
In order to use the utility client calls
|
|
3
|
+
As a developer
|
|
4
|
+
I want to make some requests and inspect some responses
|
|
5
|
+
|
|
6
|
+
@connection_needed
|
|
7
|
+
Scenario: Make a restful post to yahoo
|
|
8
|
+
When I post some data to yahoo
|
|
9
|
+
Then I should get a response
|
|
10
|
+
|
|
11
|
+
@connection_needed
|
|
12
|
+
Scenario: Make a restful get
|
|
13
|
+
When I make a restful get request
|
|
14
|
+
Then I should get a response
|
|
15
|
+
And I should see some text
|
|
16
|
+
|
|
17
|
+
@connection_needed
|
|
18
|
+
Scenario: Get some RSS
|
|
19
|
+
When I request some RSS
|
|
20
|
+
Then I should get a response
|
|
21
|
+
And I should receive some headlines
|
|
22
|
+
|
|
23
|
+
Scenario: Work with RSS
|
|
24
|
+
Given I have some RSS
|
|
25
|
+
Then I should receive some headlines
|