Testing Date: 09 April 2026
BUG Details:
Code Review Finding:
When a student purchases multiple extra items in a single checkout request, the backend updates stock and creates purchase records one item at a time. If a later item in the same request fails validation, the earlier stock reductions and purchase entries may already be saved.
Expected Output:
A multi-item checkout should behave atomically. If any item in the request fails, no stock updates or purchase records should be committed for that checkout.
Actual Output:
The backend processes items sequentially without a transaction, so a failure in the middle of the request can leave partial stock deductions and partial purchase records.
BUG Report Date: 09 April 2026
Has the bug been fixed? No
Date of BUG Fixing: N/A
Any Other Comment:
This is a backend data-integrity bug in the extras purchase flow. A single checkout request can result in a partially applied order.
Testing Date: 09 April 2026
BUG Details:
Code Review Finding:
When a student purchases multiple extra items in a single checkout request, the backend updates stock and creates purchase records one item at a time. If a later item in the same request fails validation, the earlier stock reductions and purchase entries may already be saved.
Expected Output:
A multi-item checkout should behave atomically. If any item in the request fails, no stock updates or purchase records should be committed for that checkout.
Actual Output:
The backend processes items sequentially without a transaction, so a failure in the middle of the request can leave partial stock deductions and partial purchase records.
BUG Report Date: 09 April 2026
Has the bug been fixed? No
Date of BUG Fixing: N/A
Any Other Comment:
This is a backend data-integrity bug in the extras purchase flow. A single checkout request can result in a partially applied order.