Skip to content

Commit 7487bf9

Browse files
authored
Merge pull request #41 from Yuval-Roth/testing
Testing + files to landing page
2 parents 300f426 + ec2f41a commit 7487bf9

9 files changed

Lines changed: 617 additions & 8 deletions

File tree

243 KB
Binary file not shown.
217 KB
Binary file not shown.
126 KB
Binary file not shown.
39.3 MB
Binary file not shown.
45.8 MB
Binary file not shown.
14.1 MB
Binary file not shown.
29 MB
Binary file not shown.

tests/2023-mbt-04-14/Cucumber/src/test/java/hellocucumber/StepDefinitions.java

Lines changed: 558 additions & 6 deletions
Large diffs are not rendered by default.
Lines changed: 59 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Feature: add and remove participants
22

3-
Scenario Outline: Manager adds new participant
3+
Scenario Outline: Admin adds new participant
44
Given A logged in admin user with username and password
55
And There is no participant with the email "<email>"
66
When Add participant with the email "<email>"
@@ -9,7 +9,7 @@ Feature: add and remove participants
99
| email |
1010
| tamirosh@post.bgu.ac.il |
1111

12-
Scenario Outline: Manager remove participant
12+
Scenario Outline: Admin remove participant
1313
Given A logged in admin user with username and password
1414
And There is a participant with the email "<email>"
1515
When remove the participant with the email "<email>"
@@ -18,3 +18,60 @@ Feature: add and remove participants
1818
| email |
1919
| tamirosh@post.bgu.ac.il |
2020

21+
Scenario Outline: Admin adds new operator
22+
Given A logged in admin user with username and password
23+
And There is no operator with the username "<username>"
24+
When Add operator with the username "<username>" and password "<password>"
25+
Then The operator with username "<username>" added successfully
26+
And The operator with username "<username>" and password "<password>" can log in
27+
Examples:
28+
| username | password |
29+
| tamirosh | Pass1234 |
30+
31+
Scenario Outline: Admin removes operator
32+
Given A logged in admin user with username and password
33+
And There is an operator with the username "<username>" and password "<password>"
34+
When Remove the operator with the username "<username>"
35+
Then The operator with username "<username>" removed successfully
36+
And The operator with username "<username>" and password "<password>" can't log in
37+
Examples:
38+
| username | password |
39+
| tamirosh | Pass1234 |
40+
41+
Scenario Outline: Operator can see Lobbies and Session Data functionality
42+
Given Exists an operator with the username "<username>" and password "<password>"
43+
And The operator with the username "<username>" and password "<password>" is logged in
44+
When The operator is in the main menu page
45+
Then The operator can see the Lobbies and Session Data buttons
46+
Examples:
47+
| username | password |
48+
| tamirosh | Pass1234 |
49+
50+
Scenario Outline: Operator can't see Participants and Operators functionality
51+
Given Exists an operator with the username "<username>" and password "<password>"
52+
And The operator with the username "<username>" and password "<password>" is logged in
53+
When The operator is in the main menu page
54+
Then The operator can't see the Participants and Operators buttons
55+
Examples:
56+
| username | password |
57+
| tamirosh | Pass1234 |
58+
59+
Scenario Outline: Admin creates a lobby
60+
Given A logged in admin user with username and password
61+
And There is a participant with the email "<email1>" and name "<firstname1>" "<lastname1>"
62+
And There is a participant with the email "<email2>" and name "<firstname2>" "<lastname2>"
63+
When Creates a lobby with the participants "<firstname1>" "<lastname1>" and "<firstname2>" "<lastname2>"
64+
Then The lobby with the participants "<firstname1>" "<lastname1>" and "<firstname2>" "<lastname2>" created successfully
65+
Examples:
66+
| email1 | email2 | firstname1 | firstname2 | lastname1 | lastname2 |
67+
| tamirosh@post.bgu.ac.il | tamir@mail.com | Tamir | Oshri | Avisar | Avisar |
68+
69+
Scenario Outline: Admin removes a lobby
70+
Given A logged in admin user with username and password
71+
And There is a participant with the email "<email1>" and name "<firstname1>" "<lastname1>"
72+
And There is a participant with the email "<email2>" and name "<firstname2>" "<lastname2>"
73+
When Exists a lobby with the participants "<firstname1>" "<lastname1>" and "<firstname2>" "<lastname2>"
74+
Then The lobby with the participants "<firstname1>" "<lastname1>" and "<firstname2>" "<lastname2>" can removed successfully
75+
Examples:
76+
| email1 | email2 | firstname1 | firstname2 | lastname1 | lastname2 |
77+
| tamirosh@post.bgu.ac.il | tamir@mail.com | Tamir | Oshri | Avisar | Avisar |

0 commit comments

Comments
 (0)