Built to help people learn QA by doing real QA work
What To Test is a browser-based QA/SDET practice platform for learning testing through realistic tasks: requirements analysis, test cases, bug reports, API testing, SQL, Linux, automation, and interview scenarios.
Practical QA training
Learn, practice, compare, improve.
- Format
- Browser-based labs
- Practice
- Manual QA, APIs, data, Linux, and automation
- Progress
- Stored locally in your browser
- Support
- Coaching and practical QA help for teams
Why I built this
QA is hard to learn from theory alone
Definitions matter, but practical judgment grows when you work through incomplete information, product behavior, data, integrations, and risk.
Real testing is not just knowing definitions. It is the ability to look at a feature, find unclear requirements, identify product risk, design useful checks, test APIs and data, explain failures, and communicate what matters before release.
What To Test turns that thinking into browser-based practice labs.
What you can practice
One product for the practical parts of QA
Move from core Manual QA thinking into technical workflows, automation, and interview communication.
Requirements analysis
Clarify rules, acceptance criteria, dependencies, and missing cases.
Test case design
Turn product behavior into useful positive, negative, boundary, and risk-based checks.
Bug report writing
Describe defects with reproducible steps, evidence, severity, and user impact.
API testing
Practice contracts, validation, auth, permissions, status codes, and failure behavior.
SQL practice
Validate data with practical SELECT, filtering, joins, grouping, and duplicate checks.
Linux basics
Build confidence with safe terminal commands, files, logs, and QA workflows.
Automation practice
Work through locator strategy, Page Objects, assertions, and maintainable test code.
QA interview scenarios
Explain how you would test realistic product flows and compare your coverage.
Built by Sergii Udovychenko
What To Test is built by Sergii Udovychenko, a QA/SDET engineer with 15 years of practical experience testing complex products, APIs, automation frameworks, data pipelines, payment flows, and security-sensitive systems.
This is why What To Test focuses on real QA thinking: analyzing risk, validating systems, finding weak spots, and explaining what matters before release.
View LinkedIn profileBuilt from real SDET, data, security, and product QA experience
The strongest technical areas lead the section; domain and delivery experience provide the product context behind them.
SDET and test automation
Java-based automation, API test frameworks, regression strategy, CI/CD pipelines, maintainable test architecture, and real product workflow coverage.
API, backend, and microservices testing
REST API validation, contract checks, authentication, authorization, token and session behavior, retries, errors, backend state changes, and integration risks.
ETL, data validation, and data-heavy systems
ETL/ELT testing, source-to-target checks, database consistency, data quality rules, reconciliation, and backend data verification.
Security-focused QA thinking
Auth flows, access control, role and permission boundaries, token handling, session security, abuse cases, input validation, sensitive-data exposure, and OWASP-style risk awareness.
Payments and transaction flows
Payment gateway testing, PayPal and Stripe integrations, checkout, cashier, deposits, payouts, callbacks, retries, failures, and transaction lifecycle risks.
Magento, e-commerce, and iGaming
Magento and Magento 2 commerce workflows plus iGaming products across player accounts, slots, roulette, blackjack, baccarat, cashier flows, UAT, and regression.
Practical engineering workflow
SQL, Linux, Docker, Kubernetes, GitHub and GitLab, CI/CD, logs, test data, debugging, environment issues, and QA delivery under product pressure.
What makes this different
Not just QA questions - practical QA training in the browser
Write answers, inspect scenarios, run safe simulators, compare checklist feedback, and track progress locally.
No setup required
Open a lab and start in the browser.
Safe simulators
Practice API, SQL, and Linux workflows without a real backend or shell.
Realistic scenarios
Work with product behavior, data, integrations, and risk.
Checklist feedback
Compare coverage and see what to improve next.
Local progress
Keep useful practice signals in your browser.
Beginner friendly
Build foundations through guided, practical steps.
SDET relevant
Move into technical testing, automation, and interview preparation.
Who it is for
Useful at different stages of a QA career
Start with fundamentals, sharpen technical skills, prepare for interviews, or bring the same practical approach to a team.
- People starting Manual QA
- QA engineers preparing for interviews
- QA Automation and SDET candidates
- Testers practicing API, SQL, and Linux
- Engineers who want stronger QA thinking
- Teams that need practical QA review or training
Connect or work with me
Ready to practice real QA work?
Start with guided Manual QA, explore focused labs, or ask for personal and team support.