I'm a QA Engineer who investigates products end to end — from the interface down to API contracts, databases, logs, asynchronous flows and third-party integrations.
I focus testing on business risk: payments, access control, state transitions and failure recovery. My reports connect a visible symptom to technical evidence and a clear release decision.
Good testing is not about clicking through every screen.
It's about understanding what can break — and proving what actually broke.
| Case study | Scope | Evidence and outcome |
|---|---|---|
| Telaboro | Android · Admin panel · API · PostgreSQL · Stripe · Logcat | 150+ test cases; critical payment and profile failures localized with technical evidence |
| PRTV.pro | Web · Mobile · Android TV · Billing · Integrations · Migration | 228 executed cases across 18 modules; 45 documented defects |
| ChatPlace | Telegram bot · API · Paywall · Traceability | Acceptance criteria mapped to cases, risks and evidence; release recommendation: NO-GO |
| Mailshade | Chrome extension · Exploratory testing · UX · Localization | 19 findings supported by screenshots, videos, CSV and localization analysis |
Tools and techniques
| Area | Tools and techniques |
|---|---|
| Testing | Functional · Exploratory · Regression · Integration · E2E · Risk-based |
| API & data | REST · Swagger/OpenAPI · Postman · SQL · PostgreSQL |
| Backend | Microservices · Kafka · Payments · Third-party integrations |
| Diagnostics | DevTools · Kibana · Logcat · Charles Proxy · Request/response analysis |
| Automation | Python · pytest · Playwright · Bash · GitHub Actions |
| Delivery | Git · Docker · Linux · Jira · TestRail · Confluence · CI/CD |
| Project | What it demonstrates |
|---|---|
| Monitoring Bot | Python service with marketplace integrations, defensive pricing rules, Docker and an extensive pytest suite |
| DummyJSON API Tests | Positive and negative API scenarios using Python, pytest, reusable fixtures and passing CI |
| QIWI API Tests | Payment-flow checks with Playwright APIRequestContext and a Postman collection |
Understand the product and business risk
↓
Model critical paths and state transitions
↓
Reproduce and isolate the failing layer
↓
Collect UI, API, database and log evidence
↓
Explain impact, likely cause and release risk


