Project profile
Scope, role and technology
StatusProduction / internal
RolePython automation, browser workflow design & database coordination
StackPython, Selenium, UI.Vision, Chrome, MySQL, Linux
Visual evidence
Sanitized browser-flow captures, processing-state examples, validated portal results, failure handling, and end-to-end automation evidence.
The repetitive workflow
Warranty-related tasks required navigating a third-party web portal without the API access needed for the task. Browser interaction is automated while a database-backed queue/state remains outside the browser.
Browser automation approach
- Open or resume the required browser state.
- Authenticate or detect whether an existing session is usable.
- Navigate the external portal and perform the required warranty action.
- Capture and validate the result before marking the internal item complete.
Database-backed processing state
Records retain processing state so unprocessed, pending, completed, or failed work can be distinguished and retried without corrupting history.
Architecture
MySQL queue→Python worker→Selenium / UI.Vision→External warranty portal→Validation→Status update
Engineering decisions
- Prefer APIs when available; use browser automation only where the third-party interface requires it.
- Keep queue/state in a system I control.
- Validate resulting state rather than assuming a click equals success.
- Design reruns for transient browser failures.