🐛 [Community Event] The Big Bug Hunt for Testers' Month

Generating manual test steps using AI and executing it using AI is a fun, will post many more issues. True Platform is really very good for manual tests as well

Bug title: Shipment estimated on the promised day is flagged “Late by 0 days” instead of “On time”
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100002 and click Track.
  3. Compare the Promised date (11 Sep 2026), the Estimated date (11 Sep 2026) and the Performance field.
  4. Repeat with RFL100005 (Promised 14 Sep 2026, Estimated 14 Sep 2026).

Expected result: Estimated date equal to promised date is “On time”.
Actual result: Performance shows “Late by 0 days” in red for both shipments. Delivery on the promised day is reported as late to the customer.
True Platform evidence: Katalon Platform website (test case TC-20069945, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Event filter “Transit” hides a transit event, and the event-count badge ignores the active filter
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100002 and click Track.
  3. In Scan events note that all 5 rows carry the type tag “TRANSIT” and the badge says “5 events”.
  4. Change the filter dropdown to Transit.
  5. Change the filter to Delivery.

Expected result: Step 4 keeps all 5 transit rows. The count badge shows the number of rows matching the active filter (5 for Transit, 0 for Delivery).
Actual result: Step 4 shows only 4 rows; the 07/09/2026 08:45 “Arrived at transit facility” event is dropped even though it is tagged TRANSIT (its type is stored as “Transit” with a capital T and the filter is case-sensitive). The badge still says “5 events”. Step 5 shows 0 rows and the badge still says “5 events”.
True Platform evidence: Katalon Platform website (test case TC-20069938, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Scan-events “Next” button never disables, pager goes to “Page 3 of 2” and the table disappears
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100006 and click Track.
  3. Scroll to Scan events; the pager reads “Page 1 of 2”.
  4. Click Next twice.

Expected result: Next becomes disabled on page 2 (the last page); it is impossible to go past the last page.
Actual result: The pager reads “Page 3 of 2”, the event table disappears and the message “No events match this filter.” is shown although the filter is “All events”. Further clicks give Page 4, 5, … The only way back is Previous.
True Platform evidence: Katalon Platform website (test case TC-20069921, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Scan events are sorted as text by day-of-month, not chronologically, so August events appear after September events
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100006 and click Track.
  3. Scroll to Scan events. Do not change the filter or the sort button.
  4. Read the Timestamp column on page 1, click Next, read page 2.

Expected result: Events are in date/time order: 26/08 → 28/08 → 31/08 → 02/09 → 02/09 → 03/09 → 03/09 → 03/09 (or exactly the reverse).
Actual result: Page 1 shows 02/09/2026, 02/09/2026, 03/09/2026, 03/09/2026, 26/08/2026; page 2 shows 28/08/2026, 31/08/2026, 03/09/2026. The list is ordered by the “DD/MM” text, so all August events come after the September ones. Clicking the sort button only reverses the same wrong order. The shipment history of any multi-month shipment is shown out of sequence.
True Platform evidence: Katalon Platform website (test case TC-20069872, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: High

Bug title: Tracking result shows negative progress “-20%” for a shipment in “Delivery failed” status
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100007 in the tracking field and click Track.
  3. Look at the “Shipment progress” row at the top of the result card.

Expected result: A shipment with status “Delivery failed” shows a progress value between 0% and 100% and a bar that reflects it.
Actual result: The progress label reads -20% and the progress bar is empty. A negative percentage is displayed to the customer.
True Platform evidence: Katalon Platform website (test case TC-20069840, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: High

Bug title: Create shipment accepts any value (or nothing) as Recipient phone; validation exists for sender phone only
Page version: https://logistic.rabbitfly.org/create-shipment, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/create-shipment in a new tab.
  2. Fill: Sender name Test Sender, Sender phone 0901234567, Recipient name Test Recipient, Recipient phone abc, Destination city Hue, Weight 2.
  3. Click Create shipment.
  4. Repeat with Recipient phone left empty.

Expected result: The same rule as the sender phone is applied (“Phone number must be 10 digits starting with 0”); the shipment is not created.
Actual result: In both cases “✓ Shipment created” with a tracking number appears. (Entering abc as Sender phone is correctly rejected, so the rule exists but is not applied to the recipient.)
True Platform evidence: Katalon Platform website (test case TC-20069946, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Reschedule delivery accepts a date in the past
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100004 and click Track. Scroll to Reschedule delivery.
  3. Set “New delivery date” to 01/01/2020 (any past date).
  4. Click Reschedule.

Expected result: Validation error such as “Choose a date in the future”; no success message.
Actual result: Green “Delivery rescheduled” confirmation is shown for a delivery date six years in the past. Only an empty date is rejected.
True Platform evidence: Katalon Platform website (test case TC-20069949, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Chargeable weight is rounded down to the nearest 0.5 kg, so 1.2 kg is billed as 1.0 kg
Page version: https://logistic.rabbitfly.org/rate-calculator, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/rate-calculator in a new tab.
  2. Set Actual weight 1.2, keep Length 20, Width 15, Height 10, Route Intra-city, Service Standard, COD 0, no insurance.
  3. Click Calculate rate and read Chargeable weight and Base rate.
  4. Repeat with Actual weight 1.74.

Expected result: Rate card: “First 1 kg” 15,000 then “Each extra 0.5 kg” 5,000. 1.2 kg = 1 kg + one started 0.5 kg step → chargeable 1.5 kg, base rate 20,000 VND. 1.74 kg → 2.0 kg, base 25,000 VND.
Actual result: 1.2 kg shows Chargeable weight 1.0 kg, Base rate 15,000 VND; 1.74 kg shows 1.5 kg / 20,000 VND. Weight is rounded to the nearest 0.5 kg instead of up to the next step, so every parcel between x.01 and x.24 kg over a step is under-charged by one step.
True Platform evidence: Katalon Platform website (test case TC-20069948, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Courier note limit of 100 characters is not enforced; counter goes negative but Reschedule still succeeds
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100004 and click Track. Scroll to Reschedule delivery.
  3. Pick any future date. In “Note for the courier” paste 150 characters (e.g. the letter a ×150).
  4. Click Reschedule.

Expected result: Input stops at 100 characters or an error is shown under the note; no success message.
Actual result: Counter shows “-50 characters remaining” in red, yet “Delivery rescheduled” is shown and the 150-character note is accepted.
True Platform evidence: Katalon Platform website (test case TC-20069955, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: “Pickup in progress” status badge is white text on pale yellow, fails WCAG 2.2 AA 1.4.3 Contrast (Minimum)
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100005 and click Track.
  3. Look at the Status badge at the top-right of the result card. (Optional: DevTools → Inspect the badge → Styles: color #FFFFFF, background #FDE9BF.)

Expected result: Status text is readable, like the other statuses (e.g. Delivered: dark green on light green), with contrast ≥ 4.5:1.
Actual result: What failed: 1.4.3 Contrast (Minimum). Where: the Pickup in progress status badge on the shipment card. Measured contrast white on #FDE9BF1.2:1 (required 4.5:1). Effect on the user: the shipment’s current status is practically invisible for sighted users and unreadable for low-vision users, the single most important field on the card cannot be read.
True Platform evidence: Katalon Platform website (test case TC-20069956, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Medium

Bug title: Global coverage learn more
Page version: https://logistic.rabbitfly.org/#services.
Environment (browser, OS, device): Chrome, windows
Steps to reproduce:

Expected result: Navigation to the Global coverage UI or more information
Actual result: 404 page not found
True Platform evidence:

Screenshot:
Severity: Low / Trivial

Bug title: Sea freight Learn more navigation
Page version: https://logistic.rabbitfly.org/#services.
Environment (browser, OS, device): Chrome, Windows
Steps to reproduce:

Expected result: Sea Freight UI or more information page
Actual result: 404 page not found
True Platform evidence:

Screenshot:
Severity: / Low / Trivial

Bug title: Air freight logistics Learn more navigation
Page version:https://logistic.rabbitfly.org/#services.
Environment (browser, OS, device): Chrome, Windows
Steps to reproduce:

Expected result: The Air freight Logistics UI
Actual result: 404 page not found

True Platform evidence:

Screenshot:

Severity: Low / Trivial

Bug title: Failed attempts shows “1 attempts”
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100001 and click Track; read “Failed attempts”.

Expected result: “1 attempt”.
Actual result: “1 attempts”.
True Platform evidence: Katalon Platform website (test case TC-20070021, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Trivial

Bug title: Reschedule inputs, event filter and copy button have no accessible name, fails WCAG 2.2 AA 1.3.1 / 4.1.2 / 3.3.1
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable) with NVDA screen reader, Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100004 and click Track.
  3. With a screen reader, Tab through: the Scan-events filter dropdown, the ⧉ button, “New delivery date”, “Note for the courier”. (Optional: DevTools → Accessibility pane shows Name: “” for each.)
  4. Click Reschedule with the date empty.

Expected result: Each control announces its purpose; the validation error is announced.
Actual result: What failed / where: (a) 4.1.2 Name, Role, Value: the event filter <select> has no label and the copy button’s only content is the “⧉” glyph, announced as “combo box” / “button” with no name; (b) 1.3.1 Info and Relationships: the two Reschedule labels are not associated with their inputs (no for/id), announced as “edit text” / “date”; (c) 3.3.1 Error Identification: the “Choose a new delivery date” error is not linked (aria-describedby) or announced (aria-live). Effect on the user: a screen-reader user cannot tell what to type in any reschedule field, cannot identify the filter or copy controls, and is never told why Reschedule failed.
True Platform evidence: Katalon Platform website (test case TC-20070020, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Low

Bug title: Error alert from a failed search stays on screen after a following successful search
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL999999, click Track → red alert “No shipment found with tracking number RFL999999.”
  3. Without clicking Clear results, replace the text with RFL100001 and click Track.

Expected result: The alert disappears when a new search succeeds.
Actual result: The RFL100001 card appears, but the red “No shipment found … RFL999999” alert stays above it, so a valid result is shown together with an error.
True Platform evidence: Katalon Platform website (test case TC-20070019, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Low

Bug title: “Clear form” empties the prefilled defaults, so the untouched form then fails validation
Page version: https://logistic.rabbitfly.org/rate-calculator, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/rate-calculator in a new tab; note weight 1 and dimensions 20 × 15 × 10 are prefilled.
  2. Click Clear form, then Calculate rate.

Expected result: Clear form returns the form to its initial state (defaults restored) and Calculate rate works as on first load.
Actual result: Weight and the three dimension fields are blank and Calculate rate shows four validation errors.
True Platform evidence: Katalon Platform website (test case TC-20070022, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Trivial

Bug title: “Recent searches · most recent first” lists oldest first and shows duplicates
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Track RFL100001, then RFL100002, then RFL100003, then RFL100001 again (click Track after each).
  3. Read the chips under “Recent searches · most recent first”.

Expected result: RFL100001 RFL100003 RFL100002 (most recent first, each number once).
Actual result: RFL100001 RFL100002 RFL100003 RFL100001 (oldest first and the repeated number appears twice, contradicting the label).
True Platform evidence: Katalon Platform website (test case TC-20070018, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Low

Bug title: Copy button copies the tracking number with a leading and trailing space
Page version: https://logistic.rabbitfly.org/tracking, Initial version posted 11 Sep 2026
Environment (browser, OS, device): Google Chrome (latest stable), Windows 11, desktop 1440 px
Steps to reproduce:

  1. Open https://logistic.rabbitfly.org/tracking in a new tab.
  2. Type RFL100001 and click Track.
  3. Click the ⧉ button next to the tracking number on the card.
  4. Click Clear results, click into the tracking field, press Ctrl+V, then click Track.

Expected result: Clipboard contains RFL100001 and the pasted search works.
Actual result: Clipboard contains " RFL100001 " (space before and after; visible when pasted into any text editor). The pasted search fails with "Invalid tracking number format: RFL100001 ".
True Platform evidence: Katalon Platform website (test case TC-20069987, AI run result FAILED at the verification step; run includes screenshot, video and failure analysis)
Screenshot:

Severity: Low