The QAvenue

🐝 Bee-ing a Tester: I found a bug …honey!. “Device Knows Me, App Doesn’t”. Bug #014: Autocomplete username not accepted on login.Type: UX / Functionality

Severity:

Low

Context:

When logging in, the device may auto-fill the username from previous sessions, but the application does not accept it, forcing the user to type it manually.

Steps to Reproduce:

  1. Open the login page of the application.
  2. Use the device’s autocomplete feature to fill the username field.
  3. . Enter the password manually.
  4. Click Login.

Expected Result:

  • The app accepts the username auto-filled by the device.
  • User can log in without typing the username manually.

Actual Result:

– The app rejects the username auto-filled by the device.
– Displays “Invalid username” even though it is correct.

Root Cause:

  • App validation doesn’t handle device auto-fill properly.
  • The <form> has autocomplete=”off”, preventing the app from accepting auto-filled usernames.
  • -Device auto-fill may also introduce hidden characters or formatting that the validation logic doesn’t handle.

Impact:

  • Poor user experience.
  • Frustration for users relying on autocomplete.
  • Slight increase in login errors reported to support.

Suggested Fix:

  • Trim and normalize input before validation.
  • Handle hidden characters from autocomplete.
  • Add QA tests for device auto-fill behaviour.

Lesson learnt:

” Autofill is your friend
 until it isn’t.”

Let’s connect! I share common bugs, solutions, and QA tips regularly.