Hi Everyone,
I have been testing the O3 Login environment (o3.openmrs.org/openmrs/spa/login) as part of my automation practice and GSoC preparation. After running my suite of 24 test cases, I’d like to share a few observations and potential improvements:
- Error Found (Empty Field Validation): I noticed that the login button does not provide immediate UI feedback when fields are empty (TC22). Adding a “Required” state to the Carbon Design components would prevent unnecessary API calls and improve the user experience.
- Suggested Improvement: A “Caps Lock” warning or a password visibility toggle would be highly beneficial for clinicians to reduce login failures in fast-paced environments.
- Performance: I observed a slight delay in the “Location” dropdown population upon initial load.
I have already automated these scenarios using Selenium. Should I document these as formal
Best regards, Vishnu Vardhan