Beginner QA
New to QA or light manual experience
- Assertions
- Forms
- Auth basics
- Reading failures
Est. 5 hrs
First-party QA engineering lab
Runnable UI and API labs on ITJobNotify—missions you can verify against our mock backend, challenge mode, Postman-ready collections, and learning paths for Selenium, Playwright, and REST. Build proof you can show in interviews.
Structured paths by role
New to QA or light manual experience
Est. 5 hrs
Exploratory testers adding code
Est. 10 hrs
Automation engineers before loops
Est. 8 hrs
Senior SDETs sharpening edge cases
Est. 12 hrs
On-site playground modules
Filter by scenario type, sort by difficulty or recency, then open runnable demos on ITJobNotify.
Category
Valid/invalid login, locked user, remember me, show password.
20 min
Nested cards, repeated classes, tables—stable data-testid + harder selectors.
40 min
Mock auth + CRUD + status codes against demo endpoints.
40 min
Multi-step form, required fields, regex, conditional field.
35 min
Products, cart, coupon, checkout success/failure.
45 min
Spinner, delayed content, changing text, retry.
30 min
Sort, search, pagination, row actions, selection.
35 min
Cross-page flow: sign-in screen, dashboard table, task detail—full UI navigation practice.
50 min
Interactive docs and Try it out for /api/playground/v1—items, pets, auth, reset.
35 min
Registration validation, strength hint, duplicate email, terms.
25 min
Filters, search, sort, pagination, bulk select.
40 min
Type/size checks, progress simulation, sample file link.
30 min
HTML5 drag-drop, alert, confirm, modal, tooltip.
35 min
Same-origin iframe form + shadow-root controls.
45 min
Selenium, Playwright, Cypress, Postman, REST Assured notes.
30 min
Email step, OTP simulation, invalid/expired token paths.
25 min
Roadmap: compose custom routes in-browser. The REST lab and OpenAPI explorer already expose auth, CRUD, and validation errors to script against.
45 min
Roadmap: timed chaos and retry analytics in-lab. Reproduce ordering and timing bugs on dynamic, table, and upload flows now.
40 min
Roadmap: sample pipeline configs and artifact layout. Read the automation notes for sharding, retries, and junit publishing patterns.
40 min
Roadmap: selector health scoring in UI. Compare XPath, CSS, and role-based queries on the locators and iframe/shadow modules.
35 min
Roadmap: dedicated a11y scenarios (keyboard traps, live regions, contrast). Until then, rehearse focus order and error association on the form and login modules.
40 min
Roadmap: HAR-style fixtures inside the lab. Use Playwright or Cypress route handlers against the mock API and UI modules while we ship this.
40 min
Roadmap: snapshot-friendly fixtures and diff workflow. Use the shop and locator modules to script baseline captures with your tool of choice today.
45 min
Roadmap: matrix notes per browser. The multi-page mini app is the best surface today for navigation and rendering differences across engines.
55 min
Roadmap: faker-style payloads scoped to lab entities. Seed users and catalog rows via the mock API endpoints for now.
25 min
Roadmap: scripted slow networks and Core Web Vitals hooks. Practice async readiness and perceived load on the dynamic elements module meanwhile.
50 min
Roadmap: export hooks for junit and traces from lab runs. Review the automation notes for how to wire reports and artifacts in CI today.
35 min
Roadmap: structured repro steps export. Practice tight repro narratives on drag-drop, dialogs, and the interactions module today.
30 min
Built for rehearsal, not link dumps
Execute scripts against first-party pages—no third-party demo accounts or flaky externals.
Bearer auth, CRUD, and status codes on /api/playground/v1 with Swagger UI for contract-style practice.
Append ?challenge=1 on supported modules to rehearse resilient locators like a screener whiteboard.
Default mode keeps data-testid hooks so you can learn assertions before you fight the DOM.
Auth, tables, uploads, carts, and API errors map to what teams actually ask in SDET loops.
Track opens and completions locally—pair with your repo or README when you pitch your work.
Example run summary (illustrative)
Run
Nightly UI suite
Last 7 runs — pass rate trend
Passed
184
Failed
6
Flake rate
2.4%
rolling 14d
Median time
8.4s
p95 21.4s
Trace / log
trace-chromium-7f3a.zip
Screenshot preview
Deeper write-ups paired with the lab—Selenium, Playwright, API testing, and each UI pattern.
Third-party demos (SauceDemo, The Internet, etc.) are useful references—our first-party playground above is the best place to rehearse with missions and stable hooks.
Explore tools directory →No account required. These run in your browser; saving results to a personal timeline uses your student sign-in.
First-party labs live in the Playground. External guides under /testing-tools/* point at practice patterns and our runnable demos. Pair practice with the QA career guide and SDET roadmap when you are job-searching—not only drilling tools in isolation.
Auto-waiting, tracing, and role-based locators are easier to rehearse on pages you control. Use the guide for scenarios and debugging habits, then automate the matching modules in our on-site lab.
Classic WebDriver patterns—waits, stale elements, tables, and uploads—map cleanly to our lab modules with documented demo users and stable hooks.
Exercise status codes, Bearer auth, CRUD, and validation errors against our mock REST API under /api/playground/v1—no outbound sandbox required.
Shadow DOM, nested tables, and dynamic lists are built into the lab so you can compare CSS, XPath, and accessibility-friendly queries on one domain.
Rehearse authentication UI—validation, errors, redirects, and session behavior—using lab credentials and flows designed for automation learners.
Required fields, formats, conditional inputs, and error messaging are covered in the form and signup labs with assertions you can reproduce in CI.
Cart, catalog, and checkout simulation live in our shop module—practice totals, coupons, and navigation without pointing tests at external storefronts.
Safe upload and download exercises use synthetic files and lab-only endpoints so you can focus on framework APIs and assertions.
Delayed render, spinners, and changing DOM are first-class in the dynamic and table labs—practice synchronization strategies interviewers expect you to explain.