-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #158 from soehlert/hotfix/USStateField
fix(USStateField): Don't save a US State field for non US countries
- Loading branch information
Showing
7 changed files
with
87 additions
and
38 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,70 +1,78 @@ | ||
Feature: List Views | ||
|
||
Scenario Outline: Authenticated user can view a list of entities | ||
Scenario Outline: Authenticated user can view a list of entities | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
And there is a <entity_type> in the system | ||
When I request the list of <entity_type> | ||
Then the response status code should be 200 | ||
|
||
Examples: | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
|
||
Scenario Outline: Authenticated user can create entities | ||
Scenario Outline: Authenticated user can create entities | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
When I make a new <entity_type> with valid data | ||
Then the response status code should be 302 | ||
|
||
Examples: | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
| review | | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
| review | | ||
|
||
Scenario Outline: Authenticated user can view details of entities | ||
Scenario: Authenticated user can create an international venue | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
When I create an international venue with valid data | ||
Then the response status code should be 302 | ||
And the state of the created venue should be None | ||
|
||
|
||
Scenario Outline: Authenticated user can view details of entities | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
And there is a <entity_type> in the system | ||
When I request details for that <entity_type> | ||
Then the response status code should be 200 | ||
|
||
Examples: | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
| review | | ||
| entity_type | | ||
| concert | | ||
| artist | | ||
| venue | | ||
| review | | ||
|
||
Scenario: Authenticated user can attend a concert | ||
Scenario: Authenticated user can attend a concert | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
And there is a concert in the system | ||
When I attend the concert | ||
Then the response status code should be 302 | ||
|
||
Scenario: Authenticated user can unattend a concert | ||
Scenario: Authenticated user can unattend a concert | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
And there is a concert in the system | ||
And I have attended the concert | ||
When I unattend the concert | ||
Then the response status code should be 302 | ||
|
||
Scenario Outline: Authenticated user cannot create entities with invalid data | ||
Scenario Outline: Authenticated user cannot create entities with invalid data | ||
Given I have a registered user "testuser" | ||
And "testuser" is logged in | ||
When I attempt to make a new <entity_type> with data <invalid_data> | ||
Then the response status code should be 200 | ||
Then I should see form errors in the response | ||
|
||
Examples: | ||
| entity_type | invalid_data | | ||
| concert | { "artist": "", "venue": "" } | | ||
| artist | { "name": "" } | | ||
| venue | { "name": "", "city": "", "state": "", "country": ""}| | ||
| entity_type | invalid_data | | ||
| concert | { "artist": "", "venue": "" } | | ||
| artist | { "name": "" } | | ||
| venue | { "name": "", "city": "", "state": "", "country": ""} | | ||
|