Working user order flow spec
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
Feature: Ordering a product as a user
|
||||
|
||||
@javascript
|
||||
Scenario: Happy flow
|
||||
Given There is an open supplier with a menu
|
||||
And I am signed in as a user
|
||||
And I am on the user homepage
|
||||
When the user scans a table QR code
|
||||
And the user clicks on the order 'Heineken beer' twice
|
||||
And the user clicks on the order product button 'Apple Pie'
|
||||
And the user clicks on the user order button
|
||||
Then the user should be redirected to the user order overview page
|
||||
And the user order should be created as a new order
|
||||
When the user order gets marked as being in process
|
||||
Then the user order should get feedback of being in process
|
||||
When the user order gets marked as being delivered
|
||||
Then the user order should get feedback of being delivered
|
||||
When the user orders list gets closed
|
||||
Then the user should be redirected to the archived list path
|
||||
|
||||
Scenario: Resetting an active order
|
||||
@@ -1,6 +1,6 @@
|
||||
Feature: Sign up as user using facebook
|
||||
|
||||
@javascript @broken
|
||||
@javascript
|
||||
Scenario: Happy flow
|
||||
Given There is no user information stored in the local storage
|
||||
When I visit the user obtain token path
|
||||
@@ -9,7 +9,7 @@ Feature: Sign up as user using facebook
|
||||
And I should be redirected to the user home
|
||||
And the newly created user info should be stored in the local storage
|
||||
|
||||
@javascript @broken
|
||||
@javascript
|
||||
Scenario: Already signed in user visits obtain token path
|
||||
Given I am signed in as a user
|
||||
When I visit '/user'
|
||||
|
||||
Reference in New Issue
Block a user