QA Test Report: Checkout Flow - Sprint 23 Test Period: September 15-18, 2025

QA Test Report: Checkout Flow - Sprint 23

Test Period: January 15-18, 2026

Tester: QA Team Lead

Build Version: 2.4.1

Environment: Staging

Scope: Full regression testing of checkout process including guest checkout, registered user checkout, payment processing, and order confirmation across desktop and mobile browsers.

Summary: Tested 47 test cases with 89% pass rate. Identified 5 critical bugs blocking release, 8 medium priority issues, and 3 minor cosmetic issues. The promo code functionality introduced in this sprint has significant problems that need addressing before production deployment.

Critical Issues Found: Payment gateway timeout on international cards causes complete checkout failure with no error message shown to user, only a spinning loader. Reproduced on Chrome, Firefox, and Safari across all tested card types from non US banks. This affects approximately 30% of our customer base based on analytics. Gift card balance incorrectly deducts twice when combined with credit card payment, charging customers more than order total. The order confirmation email fails to send when shipping address contains apartment numbers, leaving customers without receipt or tracking information.

Medium Priority Issues: Mobile Safari shows distorted product images in cart summary on iPhone 13 and newer models. Estimated delivery date calculation shows weekends for next day delivery option. Back button after payment confirmation returns users to empty cart instead of order summary.

Recommendations: Block release until payment gateway timeout and double charge issues are resolved as these directly impact revenue and customer trust. The email confirmation bug should also be fixed before launch since it affects post purchase experience. Mobile image distortion and delivery date issues can be addressed in a hotfix within the first week postl aunch.

I approach bug documentation by first reproducing the issue consistently to confirm it's genuine, then creating a clear record that makes it actionable for developers. A good bug report includes a descriptive title, precise steps to reproduce, the expected versus actual behavior, and environmental details like browser, device, and OS version. I always assess the severity and impact, whether it blocks critical functionality or affects an edge case, and include supporting evidence like screenshots, console errors, or screen recordings to eliminate ambiguity. The key is providing enough context that someone unfamiliar with the issue can understand, reproduce, and prioritize it without needing follow-up questions. I also note potential workarounds and whether multiple users are affected, which helps teams triage effectively and decide what needs immediate attention versus what can wait for the next sprint.

During my second year of college, I organized a career networking event that brought together alumni and current students in our department. We had about 40 students and 15 alumni professionals attend. I handled the logistics - booking the venue, coordinating with alumni relations to get contact information, sending invitations, arranging catering, and creating a structured format where students could rotate through small group conversations with different alumni every 20 minutes. One impact that really stood out was a junior student named Maria who was considering dropping out because she couldn't see how her major connected to real careers. At the event, she spoke with an alumna working in data analytics who had faced similar doubts. They exchanged contact information, and the alumna became an informal mentor to her. Maria later told me that conversation completely shifted her perspective - she ended up pursuing an internship in that field and stayed in school. She said having that direct connection made career paths feel tangible rather than abstract. The event's success taught me that thoughtful structure matters as much as just gathering people in a room. By creating those timed rotations, I ensured quieter students like Maria actually got meaningful conversations rather than being overlooked in an open networking format.