-
Notifications
You must be signed in to change notification settings - Fork 6
Attend an event test case
Serkan Özel edited this page Apr 1, 2018
·
4 revisions
Test Case #3
Change Profile: …
Description: Test if can attend a previously created event.
Design Time: 01.04.2018
Designed by: Serkan Özel
Execution Time: …
Executed by: …
Related Requirement:
- willAttendUser (Req: 1.2.6.1, 1.2.6.3)
- maybeAttendUser (Req: 1.2.6.1, 1.2.6.3)
- notAttendUser (Req: 1.2.6.1, 1.2.6.3)
- attendedUser (Req: 1.2.6.2)
- notAttendedUser (Req: 1.2.6.2)
- eventList (Req: 1.2.11.1.2 and 1.2.11.1.3)
Preconditions:
- User have successfully logged in.
- User navigated to a event page.
- Event is not private
Steps:
- Fill in age, attendants, sexuality and press ok.
- Choose payment method.
- Click attend event button in the page.
- In the prompt windows popped up enter e-mail and phone number.
- Press ok.
- Enter credit card information.
- Complete transaction via connecting to bank's system.
- Print/Download the ticket created.
Step | Action | Expected System Response | Pass/Fail | Comment |
1 | Fill in ages and genders of attendants and press ok. | Show typed text in the textbox. Call event.update(information) | – | – |
2 | Choose payment method. | If it is credit card, open credit card information entry page, else if remitment, show remitment account information. | – | – |
3 | Click attend event button in the page. | Prompt e-mail and phone from user into textboxes. | – | – |
4 | Press ok. | If given values in [email protected] and xxx-xxx-xx-xx format, store the values and continue to credit card information page. Call event.update(information) | – | – |
5 | Enter credit card information. | Show entered values on the screen. | – | – |
6 | Complete transaction via connecting to bank's system. | If the bank's response is a fail, show error message and return to step 5. If it succeeds, go to ticket print page. | – | – |
6 | Print/Download the ticket created. | Create ticket file. When download button pressed, serve the ticket file to user. | – | – |
Postconditions:
- The user is now willAttendUser of the event.
- Payment data is stored.
- Ticket file is stored.