Перейти до основного вмісту

Testing Cases

This document outlines core functional and edge test cases across services.


1. User Service

IDTest DescriptionType
U001Register with valid email/passUnit
U002Register with existing emailUnit
U003Login with correct credentialsUnit
U004Login with wrong passwordUnit
U005JWT token expirationUnit

2. Booking Service

IDTest DescriptionType
B001Book seat on available routeIntegration
B002Book same seat twiceIntegration
B003Booking timeout (no payment in 15 mins)Unit + E2E
B004Cancel confirmed bookingIntegration
B005Retry failed bookingUnit

3. Payment Service

IDTest DescriptionType
P001Initiate payment and succeedE2E
P002Payment fails due to gateway timeoutIntegration
P003Refund confirmed paymentIntegration
P004Invalid booking ID on paymentUnit

4. Notifications

IDTest DescriptionType
N001Email sent on booking confirmationIntegration
N002SMS fallback when email failsIntegration
N003Handle external API outage gracefullyUnit

  • Document Version: 1.0
  • Date: 2025-06-23
  • Author: ArturChernets