-
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 #81 from Arc-E-Tect/refresh-versions
Upgrade gradle dependencies
- Loading branch information
Showing
17 changed files
with
410 additions
and
329 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
315 changes: 140 additions & 175 deletions
315
src/bdd-test/java/com/arc_e_tect/blog/phonebook/web/contacts/ContactSteps.java
Large diffs are not rendered by default.
Oops, something went wrong.
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
80 changes: 41 additions & 39 deletions
80
src/bdd-test/resources/com/arc_e_tect/blog/phonebook/web/contacts/add_a_contact.feature
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,48 +1,50 @@ | ||
Feature: Add a contact to the phonebook | ||
|
||
Scenario: 01 - A new contact | ||
Given the contact with name "Peter Parker" is not listed in the phonebook | ||
When the contact is added to the phonebook | ||
| name | phone | | ||
| Peter Parker | +1 (555) 432748 | | ||
Then the phonebook contains the contact with name "Peter Parker" | ||
And the contact with name "Peter Parker" has phone number "+1 (555) 432748" | ||
And the response contains the contact with name "Peter Parker" | ||
And the response contains the contact with phone "+1 (555) 432748" | ||
Given the phonebook is empty | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 42 | Peter Parker | +1 (555) 432748 | | ||
Then the response contains the new contact "Peter Parker" with phone "+1 (555) 432748" | ||
|
||
Scenario: 02 - A contact with no name | ||
When the contact with no name is added to the phonebook | ||
Then the phonebook does not contain a contact with no name | ||
And the response is an error indicating that invalid contact data was provided | ||
Scenario: 02 - A new contact without a phone | ||
Given the phonebook is empty | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 42 | Peter Parker | [blank] | | ||
Then the response contains the new contact "Peter Parker" with phone "" | ||
|
||
Scenario: 03 - A contact with an empty string as name | ||
When the contact with name "" is added to the phonebook | ||
Then the phonebook does not contain a contact with no name | ||
And the response is an error indicating that invalid contact data was provided | ||
|
||
Scenario: 04 - An already listed contact | ||
Given the contact with name "John Smith" is listed in the phonebook | ||
When the contact with name "John Smith" is added to the phonebook | ||
Then the response is an error indicating that a contact with the same name already exists | ||
Scenario: 03 - A contact with the same name as a listed Contact | ||
Given the listed contact | ||
| id | name | phone | | ||
| 42 | Peter Parker | +1 (555) 748432 | | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 1 | Peter Parker | +1 (555) 432748 | | ||
Then the response contains the new contact "Peter Parker" with phone "+1 (555) 432748" | ||
|
||
@ignore | ||
Scenario: 04 - An already listed contact | ||
@error | ||
Scenario: 04 - A contact with the same id as a listed Contact | ||
Given the listed contact | ||
| name | phone | | ||
| Peter Parker | +1 (555) 748432 | | ||
When the contact is added to the phonebook | ||
| name | phone | | ||
| Peter Parker | +1 (555) 432748 | | ||
Then the phonebook contains the contact with name "Peter Parker" | ||
And the contact with name "Peter Parker" has phone number "+1 (555) 432748" | ||
And the response contains the contact with name "Peter Parker" | ||
| id | name | phone | | ||
| 42 | Peter Parker | +1 (555) 748432 | | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 42 | Peter Parker | +1 (555) 432748 | | ||
Then the response is an error indicating that the contact already exists | ||
|
||
Scenario: 05 - A new contact | ||
Given the contact with name "Peter Parker" is not listed in the phonebook | ||
When the contact is added to the phonebook | ||
| name | phone | | ||
| Peter Parker | | | ||
Then the phonebook contains the contact with name "Peter Parker" | ||
And the contact with name "Peter Parker" has no phone number | ||
And the response contains the contact with name "Peter Parker" | ||
@error | ||
Scenario: 05 - A contact without an empty name is added | ||
Given the phonebook is empty | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 42 | [blank] | +1 (555) 432748 | | ||
Then the response is an error indicating that the contact details are invalid | ||
|
||
@error | ||
Scenario: 06 - A contact without a name is added | ||
Given the phonebook is empty | ||
When adding to the phonebook the contact | ||
| id | name | phone | | ||
| 42 | | +1 (555) 432748 | | ||
Then the response is an error indicating that the contact details are invalid |
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
Oops, something went wrong.