Less manual entry across orders, payments, and reporting.
01 · Context
Less manual entry across orders, payments, and reporting.
The problem
Orders, inventory, payments, and reporting were spread across several systems. Entering and reconciling data by hand took time and created opportunities for errors.
My role
I worked as a contract SDET · QA Automation Engineer from April 2024 to August 2025. The linked repositories show related automation and test engineering work.
02 · Engineering decisions
How it works.
- 01Use Python automation to connect business workflows.
- 02Apply a Page Object Model to Playwright UI checks.
- 03Validate API contracts and income/expense data with focused checks.
- 04Separate business services from Telegram and serverless entry points in Pombot.
- Commerce · payment APIs
- Python services
- Sheets · Telegram
- Regression checks
03 · Quality strategy
How I tested it.
The client experience includes API, unit, integration, and regression checks. The public POM and Pombot repositories provide separate views of test architecture and application behavior.
04 · Result & reflection
Results so far.
The work reduced manual entry by approximately 60% across three platforms and saved more than 10 hours of reconciliation per month.
Scope & limitations
These results come from the client engagement. The public repositories were published later and show related work, rather than an exact snapshot of the client system.
What I learned
The checks need to follow data across systems. A working storefront alone doesn’t tell you whether payments and financial reports reconcile correctly.
