I'm a QA Engineer working across the full product path — UI → API → database → logs → integrations → failure recovery → release decision.
My strongest area is production-oriented manual QA with technical diagnostics: payments, authorization, state transitions, mobile/web behavior, third-party integrations and backend failures. I use Python for API automation, test tooling and production automation projects.
Good testing is not about clicking through every screen.
It's about understanding what can break — and collecting enough evidence to prove what actually broke.
Open-source Python automation for marketplace sellers: competitor monitoring, seller-side repricing, order-chat operations and Telegram control.
Stack: Python · Telegram Bot API · GGSEL/DigiSeller APIs · SQLite · Docker · GitHub Actions · pytest
Engineering focus:
- isolated marketplace/product profiles;
- resilient competitor parsing and seller API integration;
- price floors, cooldowns, weak-signal filters and idempotent writes;
- fail-closed
DRY_RUNboundary; - non-root Docker runtime, health checks, CI and security verification.
Repository → · Stable release → · Safe demo → · Architecture →
| Case study | Scope | Evidence and outcome |
|---|---|---|
| AI SaaS Platform | AI runtime · agents · HTTP/OpenAPI integrations · responsive/E2E | 150+ checks, 20+ defects, P0/P1 risk coverage |
| PRTV.pro | Web · Mobile · Android TV · Billing · Integrations · Migration | 228-case suite, 45 documented defects |
| Telaboro | Android · Admin · API · PostgreSQL · Stripe · Logcat | 150+ cases, release-blocking payment/profile failures localized |
| ChatPlace | Telegram bot · API · paywall · traceability | release NO-GO with acceptance criteria, risks and blocker evidence |
| Mailshade | Chrome extension · Gmail · exploratory · UX · localization | 19 findings with screenshots/video/CSV evidence |
| Android TV QA | Playback · cache · offline USB · schedules | scenario-based defects with runtime evidence |
Tools and techniques
| Area | Tools and techniques |
|---|---|
| Testing | Functional · Smoke · Sanity · Regression · Integration · E2E · Acceptance · Exploratory · Risk-based |
| API & data | REST · Swagger/OpenAPI · Postman · SQL · PostgreSQL |
| Backend | Microservices · Kafka · payments · persistence · third-party integrations |
| Diagnostics | DevTools · Kibana · Logcat · Charles Proxy · Network/Console · request/response analysis |
| Automation | Python · pytest · Playwright · requests · FastAPI · GitHub Actions |
| Delivery | Git · Docker · Linux · GitLab CI · Jira · TestRail · Allure |
| Project | What it demonstrates |
|---|---|
| Exportum Bot | Telegram FSM workflows, role separation, reporting, Google Sheets integration and CI |
| Orcestre | PostgreSQL/SQLAlchemy, scheduling, rate controls, diagnostics, Docker and Telegram operations |
| Proxy Seller Desktop Launcher | Python/Tkinter desktop automation around Proxy-Seller API and system proxy configuration |
| DummyJSON API Regression Suite | pytest/requests fixtures, auth/cart coverage, negative scenarios, CI and dependency audit |
| Nebus / QIWI Payment API Suite | Playwright APIRequestContext, payment-flow validation, Postman and safe CI collection |
Understand product and business risk
↓
Model critical paths / state transitions
↓
Reproduce and isolate the failing layer
↓
Collect UI + API + DB + logs evidence
↓
Build and verify a root-cause hypothesis
↓
Retest the fix + affected regression
↓
Make a release decision
- monitoring-bot — production Python automation, integrations, safety controls and operations.
- commercial-ai-saas-qa — commercial QA methodology, E2E coverage and sanitized defect evidence.
- Telaboro-QA-Case- — Android/API/payment investigation with Logcat evidence.
- PRTV.pro — broad release-readiness assessment across Web/Mobile/TV.
- Exportum Bot — production Telegram automation for agricultural logistics workflows, multi-role state transitions, reporting and CI.
🌐 vsevolodqa.ru · 💬 @vsevolod_qa
QA and engineering work grounded in real product behavior and technical evidence.