Web: Testing main issue

[stefanhopman1]

Wiki: https://github.com/domits1/Domits/wiki/Testing-101

step 1: Local testing step 2: automated testing via Github step 3: Slack notification per pr request if tests fail

• [ ] Web: Test: Guest: Login
• [ ] Web: Test: Guest: Register
• [ ] #159
• [ ] #624
• [ ] #625
• [ ] #626
• [x] #590
• [x] #591
• [x] #592
• [ ] #593
• [ ] #594
• [ ] #595
• [ ] Web: Test: Host: Login
• [ ] Web: Test: Host: Register
• [x] #160
• [ ] #596
• [ ] #597
• [ ] #598
• [ ] #599
• [ ] Web: Test: Host dashboard (Revenues tab)
• [ ] #600
• [ ] Web: Test: Host dashboard (Occupancy/ADR tab)
• [ ] #601
• [ ] Web: Test: Host dashboard (Property care tab)
• [ ] Web: Test: Host dashboard (IoT Hub tab)
• [ ] Web: Test: Host dashboard (Pricing tab)
• [ ] Web: Test: Host dashboard (Distribution tab)
• [ ] Web: Test: Host dashboard (Monitoring tab)
• [ ] Web: Test: Host dashboard (Screening tab)
• [ ] #602
• [ ] #604
• [ ] #603
• [ ] Web: Host dashboard (Promo codes tab)

Tools: https://www.cypress.io/ https://jestjs.io/

[giannivanlooij]

currently seting up a cypress automated test env

[Timmhart]

Host experience

User story

As a tester, I want to ensure that the host dashboard and accommodation onboarding process function smoothly, so hosts can efficiently manage their properties and complete onboarding without issues.

Example mapping

• What if the host onboarding is interrupted (e.g., due to a network issue)?
  • The system should save progress, allowing the host to resume the onboarding process from where they left off.
• What if the host enters invalid data during onboarding (e.g., invalid registration number)?
  • The system should display a clear error message, preventing the host from moving forward until the issue is resolved.
• What if a host manages multiple properties?
  • The dashboard should display all properties accurately, allowing the host to switch between them for management.
• What if the host’s dashboard does not load correctly?
  • The system should provide a fallback option with basic error handling, and the issue should be logged for troubleshooting.

Accept criteria

• [ ] The host dashboard should load correctly, displaying key metrics such as total bookings, revenue, and upcoming check-ins.
• [ ] The tester should verify that all buttons, links, and navigations work as expected within the host dashboard (e.g., accessing property management, checking booking status, viewing notifications).
• [ ] The accommodation onboarding process should guide the host through each step, including property details, photos, pricing, availability, and registration numbers, without glitches.
• [ ] Error handling should be tested, ensuring that incorrect or incomplete inputs during onboarding trigger clear error messages and prompt corrections.
• [ ] The dashboard should accurately reflect updates made during onboarding (e.g., when a new property is added, it should appear in the dashboard with correct details).
• [ ] The tester should verify that all form fields are validated properly and save data correctly during onboarding.
• [ ] Notifications and alerts should trigger appropriately when tasks are completed (e.g., property listed successfully or missing registration numbers).
• [ ] The system should allow hosts to update existing property details from the dashboard, and the changes should reflect correctly across the platform.

[Timmhart]

Guest experience

User story

As a tester, I want to ensure that the guest dashboard and booking engine work seamlessly, so guests can book accommodations and manage their reservations without any problems.

Example mapping

• What if the guest selects unavailable dates during booking?
  • The system should prevent the booking from going through and suggest alternative dates or accommodations.
• What if the guest’s payment fails?
  • The booking engine should display a clear error message and offer options for retrying the payment or selecting a different method.
• What if the guest dashboard does not load correctly?
  • The system should provide a fallback option or display a maintenance message while logging the issue for further review.
• What if the guest wants to cancel a booking?
  • The system should guide the guest through the cancellation policy, and the dashboard should update the status accordingly after the cancellation is confirmed.

Accept criteria

• [ ] The guest dashboard should load properly, displaying upcoming trips, booking history, and any relevant notifications.
• [ ] The tester should verify that the booking engine allows guests to smoothly select dates, view available accommodations, and complete bookings.
• [ ] The booking engine should calculate prices correctly, including any applicable discounts, fees, or taxes, and display the breakdown to the guest before confirming.
• [ ] The tester should ensure that all filters (e.g., price, location, amenities) work properly during the search process.
• [ ] Once a booking is made, the guest dashboard should update with the correct details, including accommodation information, dates, and booking status.
• [ ] Error handling during the booking process should be tested, ensuring that issues like invalid payment details or unavailable dates are handled gracefully.
• [ ] The guest should receive an accurate confirmation after booking, both in the dashboard and via email.
• [ ] The guest should be able to modify or cancel bookings from the dashboard if allowed, and any changes should be reflected in the system.