Acceptance Test ‐ Mehmet Kaan Ünsel - bounswe/bounswe2026group11 GitHub Wiki
Acceptance Test: Protected Event Time Change Reconfirmation
Test Case Information
| Field |
Value |
| Test Case ID |
TC_MOBILE_EVENT_RECONFIRMATION_01 |
| Test Title |
Protected event time change requires participant reconfirmation |
| Priority |
Very High |
| Module |
Mobile Event Detail, Ticket Detail, Notifications, Participation |
| Designed By |
Mehmet Kaan Ünsel |
| Date Designed |
2026-04-30 |
| Planned Execution Date |
2026-05-09 |
| Automated |
No |
| Status |
Not Run |
Description
This acceptance test verifies that when a host changes the start time of a protected event, an already participating user is notified, moved into a reconfirmation state, blocked from generating a QR ticket, redirected correctly through the notification deep link, and able to cancel participation. Canceling participation must also cancel the related ticket.
Test Data
Since this test will be executed on 2026-05-09, “tomorrow” means 2026-05-10.
| Data Type |
Value |
| Host name |
Ayşe Demir |
| Host email |
[email protected] |
| Participant name |
Mehmet Kaan Ünsel |
| Participant email |
[email protected] |
| Event title |
Protected Jazz Night |
| Event privacy level |
PROTECTED |
| Initial event date/time |
2026-05-10 20:00 |
| Updated event date/time |
2026-05-10 16:00 |
| Expected notification title |
Event time changed |
| Expected notification message |
Protected Jazz Night now starts at 16:00 instead of 20:00. Please confirm or cancel your participation. |
Required Data Setup
| # |
Setup Item |
Required State |
| 1 |
Create host user |
Ayşe Demir, [email protected] |
| 2 |
Create participant user |
Mehmet Kaan Ünsel, [email protected] |
| 3 |
Create protected event |
Protected Jazz Night, scheduled for 2026-05-10 20:00, hosted by Ayşe Demir |
| 4 |
Add participant to event |
Mehmet Kaan Ünsel is already approved/participating |
| 5 |
Create ticket |
Participant has an active ticket for the protected event |
| 6 |
Enable notifications |
Participant has push notifications enabled on mobile |
| 7 |
Prepare in-app notifications |
Notification center is available in the app |
Pre-conditions
| # |
Condition |
| 1 |
Host is logged in and can edit the event. |
| 2 |
Participant is logged in on mobile. |
| 3 |
Participant is already participating in the protected event. |
| 4 |
Participant has an active ticket before the event time change. |
| 5 |
Push notifications and in-app notifications are enabled. |
Test Steps
| Step |
Action |
Expected Result |
| 1 |
Participant opens Protected Jazz Night event detail page. |
Event time is shown as 2026-05-10 20:00; participant is shown as participating. |
| 2 |
Participant opens ticket detail page. |
Ticket is active and QR generation is available. |
| 3 |
Host changes event time from 20:00 to 16:00 on 2026-05-10. |
Event update is saved successfully. |
| 4 |
System processes the time change. |
Participant status changes to waiting for reconfirmation; ticket status changes to PENDING. |
| 5 |
Check participant phone notification center. |
Push notification appears for the event time change. |
| 6 |
Check in-app notification center. |
Unread in-app notification appears with the same event time change message. |
| 7 |
Participant taps the phone notification. |
Deep link opens the event detail page for Protected Jazz Night. |
| 8 |
Participant checks event detail page. |
UI clearly shows the time shift: 20:00 -> 16:00. |
| 9 |
Participant checks available actions. |
Two options are visible: Continue Participation and Cancel Participation. |
| 10 |
Participant opens ticket detail page again. |
Ticket status is PENDING; QR generation is unavailable. |
| 11 |
Participant returns to event detail and clicks Cancel Participation. |
Participation cancellation succeeds. |
| 12 |
Verify final state. |
Participant is no longer participating, and the ticket is CANCELED. |
Expected Results
| Area |
Expected Result |
| Event |
Event time changes from 2026-05-10 20:00 to 2026-05-10 16:00. |
| Participation |
Participant is moved into a reconfirmation/waiting state after the time change. |
| Ticket |
Ticket changes from active to PENDING; after cancellation it becomes CANCELED. |
| QR |
Participant cannot generate a QR code while ticket is PENDING or CANCELED. |
| Push notification |
Participant receives a phone notification about the time change. |
| In-app notification |
Participant sees the event time change in the notification center. |
| Deep link |
Tapping the notification opens the correct event detail page. |
| UI |
Event detail clearly displays 20:00 -> 16:00. |
| Cancellation |
Canceling participation cancels both participation and ticket. |
Actual Result
Not executed yet.
Post-condition
| Item |
Final Expected State |
| Event |
Active, scheduled for 2026-05-10 16:00 |
| Participant |
No longer participating after cancellation |
| Ticket |
CANCELED |
| QR |
QR generation unavailable |
| Notification |
Event time change notification remains visible in notification history |
Pass / Fail Criteria
The test passes if all expected results are observed. The test fails if the participant is not notified, is not moved into reconfirmation, can still generate a QR code with a pending ticket, is not redirected correctly by the notification, cannot see the 20:00 -> 16:00 change, or cancellation does not cancel both participation and ticket.
Notes
This test includes behavior that may not be fully implemented yet, especially event-update reconfirmation and pending ticket handling. It defines the expected acceptance behavior for the completed feature.