Better user specs for joining tables
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
Feature: Joining an occupied table
|
||||
|
||||
@javascript
|
||||
Scenario: Happy flow
|
||||
Given There is an open supplier with a menu
|
||||
And there is a signed in user with an active order
|
||||
And I am on the user homepage
|
||||
When another user scans the QR code on the table
|
||||
And the other user clicks the join table button
|
||||
Then the other user should see a join table waiting message
|
||||
And the original user should see a join request message
|
||||
When the original user approves the other user's join request
|
||||
Then the original user should not see the join request anymore
|
||||
And the other user should be added to the active list
|
||||
And the other user should be redirected to the user menu page
|
||||
|
||||
@javascript
|
||||
Scenario: Original user rejects the join request
|
||||
Given There is an open supplier with a menu
|
||||
And there is a signed in user with an active order
|
||||
And I am on the user homepage
|
||||
When another user scans the QR code on the table
|
||||
And the other user clicks the join table button
|
||||
Then the other user should see a join table waiting message
|
||||
And the original user should see a join request message
|
||||
When the original user rejects the other user's join request
|
||||
Then the original user should not see the join request anymore
|
||||
And the other user should not be added to the active list
|
||||
And the other user should see a join reject message
|
||||
|
||||
#@javascript
|
||||
#Scenario: The other user just wants to see the table menu
|
||||
#Given There is an open supplier with a menu
|
||||
#And there is a signed in user with an active order
|
||||
#And I am on the user homepage
|
||||
#When another user scans the QR code on the table
|
||||
#And the other user clicks the show me the menu button
|
||||
Reference in New Issue
Block a user