MasjidIslamic EventTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025Test Scenario ReportTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not suppTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfeTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
ssional format or not and for next time give same format always iTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
f perfect
ort registration, but it accurately rendered the event thumbTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format alwaTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
ys if perfect
nail pulled froTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
format or not and for next tTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
ime give same formatTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
always if Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
perfTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
ect
m the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11)
CMZWeb (Web)
CMZWeb Mobile App (web-wrapped)
CMZWeb Widgets
CMZWeb TV Display
🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process.
🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule.
Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly.
CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal.
Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message.
Bug Identified
The event detail page (before registration) showed the correct time.
The registration success message and confirmation email/ticket both displayed an outdated or incorrect time.
Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata.
TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct.
Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms.
✅ Test Outcome Event creation and registration work as expected across all platforms.
Notifications, redirection, and ticket generation are functional.
One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect
4th Cross, Chikkana LayTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025Test Scenario ReportTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not suppTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfeTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ssional format or not and for next time give same format always iTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect f perfect ort registration, but it accurately rendered the event thumbTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format alwaTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ys if perfect nail pulled froTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect format or not and for next tTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ime give same formatTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect always if Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect perfTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ect m the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfectout, Kammangggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggahalli, Bengaluru, Karnataka, India
4th Cross, Chikkana LayTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025Test Scenario ReportTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not suppTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfeTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ssional format or not and for next time give same format always iTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect f perfect ort registration, but it accurately rendered the event thumbTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format alwaTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ys if perfect nail pulled froTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect format or not and for next tTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ime give same formatTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect always if Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect perfTest Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect ect m the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Test Scenario Report Test Scenario Title: End-to-End Event Registration – Multi-Platform Validation Test Date: 15 July 2025 Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfect Project: CMZWeb Test Environment: Admin Portal (Chrome, Windows 11) CMZWeb (Web) CMZWeb Mobile App (web-wrapped) CMZWeb Widgets CMZWeb TV Display 🔍 Scenario Description This scenario verifies the complete event creation and registration flow across all CMZWeb platforms. The test focuses on validating content consistency, ticket generation, user notification, and bug detection during a free event registration process. 🔄 Test Flow Event Creation via Portal A new free event was created through the CMZWeb Admin Portal with a total capacity of 29 seats. The event required user registration. After saving the event, it was successfully added to the system with all expected attributes — title, description, image, and schedule. Mobile Notification Trigger Immediately after creation, two mobile push notifications were received, notifying the user that a new event has been added. This confirms that real-time alerts from the portal are functioning correctly. CMZWeb (Desktop Browser) Registration Flow The user accessed the CMZWeb website, located the newly created event, and opened the event detail page. The event was listed correctly with its basic information. The user clicked on Register, and the registration was processed. A “Registration Successful” message appeared on the page. However, this success box showed the wrong event timing, which did not match the correct time configured in the portal. Following registration, the user also received a confirmation email containing a virtual ticket. The email content correctly included the event name and registration ID, but it also displayed the same incorrect event time as seen on the webpage's success message. Bug Identified The event detail page (before registration) showed the correct time. The registration success message and confirmation email/ticket both displayed an outdated or incorrect time. Widgets Platform Behavior Accessing the widget (embedded on another site or mini-view) and clicking the event correctly redirected to the CMZWeb event page. The user followed the same registration process and encountered the same issue — the confirmation message and email showed the wrong timing, even though the event detail page had the correct schedule. This confirms that the bug is not platform-specific but tied to how the backend processes registration metadata. TV Display Validation On the CMZWeb TV platform, the event image was correctly displayed along with the event title. As expected, the TV version does not support registration, but it accurately rendered the event thumbnail pulled from the portal. This verifies that TV-side syncing is operational and visually correct. Mobile App Registration Flow The mobile app, which loads a mobile view of the CMZWeb site, displayed the event correctly in its list. The user followed the same procedure: opened the event, registered successfully, saw the success message, and received an email confirmation. As with web and widget, the event timing in the confirmation box and email was incorrect, confirming consistent bug behavior across platforms. ✅ Test Outcome Event creation and registration work as expected across all platforms. Notifications, redirection, and ticket generation are functional. One critical bug was identified regarding event timing inconsistencies. ✅ Final Platform Status 🌐 CMZWeb Web: ❌ Failed (Timings issue) 📱 CMZWeb Mobile App: ❌ Failed (Timings issue) 🧩 CMZWeb Widgets: ✅ Passed 📺 CMZWeb TV: ✅ Passed just go though all check this is porfessional format or not and for next time give same format always if perfectout, Kammangggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggahalli, Bengaluru, Karnataka, India
Follow
