Skip to content

Commit

Permalink
Update Visit.feature
Browse files Browse the repository at this point in the history
Correções pós revisão do professor Paulo.
  • Loading branch information
marcelloclv committed May 21, 2014
1 parent 6c0da38 commit 04ce279
Showing 1 changed file with 17 additions and 12 deletions.
29 changes: 17 additions & 12 deletions test/cucumber/Visit.feature
Original file line number Diff line number Diff line change
Expand Up @@ -78,32 +78,37 @@ Feature: Visit

Scenario: list existing visits and periods
Given the system has visits with initial or final date greater than or equal "01/01/2011"
When I view the list of visits
Then the list is returned with a list of visits with initial or final date greater than or equal "01/01/2011"
When I list the visits for the period from "01/01/2011" to today
Then no data is stored by the system

Scenario: visit for a stored visitor
Given the system has visitor named "Person"
When I try to create the visit for the visitor "Person"
Then the system asks if this visitor is the already registered visitor "Person"
And the visit for the visitor "Person" is not properly stored by the system
Given the system has a visitor named "Person"
When I try to create a visit for the visitor "Person"
Then the visit for the visitor "Person" is not properly stored by the system

Scenario: asking identification for a visitor that already exists
Given I am logged as "admin" and at the Add Visit Page
And the system has visitor named "Person"
Given I am logged as "admin"
And I am at the Add Visit Page
And the system has a visitor named "Person"
When I try to create a visitor named "Person"
Then the Confirm Identification Page is open

Scenario: confirming identification for a visitor that already exists
Given I am logged as "admin" and at the Confirm Identification Page
Given I am logged as "admin"
And I have tried to create a visit for a visitor that already exists
And I am at the Confirm Identification Page
When I press the "Yes" button
Then the visit for the visitor is properly stored by the system

Scenario: changing the name of a visitor that already exists
Given I am logged as "admin" and at the Confirm Identification Page
Given I am logged as "admin"
And I have tried to create a visit for a visitor that already exists
And I am at the Confirm Identification Page
When I press the "No" button
Then a new visitor is created with a different name and properly stored by the system
Then a new visitor is created with a different name
And the new visitor is properly stored by the system
And the visit for the new visitor is properly stored by the system

#if( $Twitter )
Scenario: Add a new visit twitting it
Given I am logged as "admin" and at the Add Visit Page
Expand Down

0 comments on commit 04ce279

Please sign in to comment.