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.
Selected paid QA projects with public, sanitized artifacts.
| Project | Scope | Evidence and outcome |
|---|---|---|
| PRTV.pro | Web · Mobile · Android TV · Billing · Integrations · Migration | 228-case suite across 18 modules; 45 documented defects |
| Telaboro | Android · Admin panel · API · PostgreSQL · Stripe · Logcat | 150+ test cases; critical payment and profile failures localized with technical evidence |
| Mailshade | Chrome extension · Exploratory testing · UX · Localization | 19 findings supported by screenshots, videos, CSV and localization analysis |
| Android TV Slideshow App | Android TV · Offline USB · Cache · Collections · Scheduled streams | Executed cases linked to scenario-based defects and runtime/video evidence |
Tools and techniques
| Area | Tools and techniques |
|---|---|
| Testing | Functional · Exploratory · Regression · Integration · E2E · Risk-based |
| API & data | REST · Swagger/OpenAPI · Postman · SQL · PostgreSQL |
| Backend | Payments · state transitions · persistence · third-party integrations |
| Diagnostics | Chrome DevTools · Firefox DevTools · Network · Console · Kibana · Logcat · Charles Proxy · request/response analysis |
| Test management | Jira · TestRail · Allure TestOps · Confluence |
| Learning / automation | Python · pytest · Playwright · Bash · GitHub Actions · GitLab CI |
| Delivery | Git · Docker · Linux · CI/CD |
Python is my current learning track for QA automation, API checks, fixtures and small test tooling.
| Project | What I'm practicing |
|---|---|
| DummyJSON API Tests | Positive and negative API scenarios using Python, pytest, reusable fixtures and CI |
| QIWI API Tests | Payment-flow checks with Playwright APIRequestContext and a Postman collection |
| QA Automation Roadmap | Python basics, validation logic and pytest practice |
Older engineering projects
These are older experiments that I keep as part of the path:
- Monitoring Bot — marketplace integrations, pricing logic, Docker and pytest coverage.
- Orcestre — Telegram automation, scheduling, persistence and API interaction.
- Exportum Bot — Telegram workflow automation for logistics operations.
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
Building, testing and investigating how products really work.