Login Demo
Practice login flows, validation messages, locked users, invalid credentials, and logout behavior.
Available
Open demo →QA Automation Practice Platform
QA Labs is a future practice platform for automation engineers. It will include web UI demos, API endpoints, stable selectors, test data, and scenario documentation designed for tools like Selenium, Cypress, Playwright, Robot Framework, and API testing frameworks.
Purpose
QA Labs will provide a structured environment where automation engineers can practice common testing scenarios without relying on fragile or outdated demo websites.
Every demo page will be designed with clear flows, predictable data, useful UI states, and stable selectors such as data-testid.
Demo Pages
Level 1
Core UI automation examples for learning the most common web testing flows.
Practice login flows, validation messages, locked users, invalid credentials, and logout behavior.
Available
Open demo →Practice inputs, dropdowns, checkboxes, radio buttons, validation states, and form submissions.
Available
Open demo →Practice search, filtering, sorting, pagination, row validation, and row actions.
Available
Open demo →Practice links, menus, breadcrumbs, active states, redirects, and route validation.
Available
Open demo →Practice stable locators using data-testid, CSS selectors, XPath, text, roles, and attributes.
Available
Open demo →Practice calendars, date pickers, time inputs, date ranges, and date validation scenarios.
Available
Open demo →Level 2
Practice common browser interactions used in real-world automation.
Practice file inputs, drag and drop uploads, file validation, upload progress, and success/error states.
Available
Open demo →Practice file downloads, generated files, download states, progress indicators, download history, and validation scenarios.
Available
Open demo →Practice iframe switching, embedded content, frame-specific selectors, parent messages, and iframe validations.
Available
Open demo →Practice new tabs, popup windows, same-tab navigation, child pages, parent messages, and browser context validation.
Available
Open demo →Practice scroll navigation, sticky headers, back-to-top behavior, lazy loaded cards, infinite scroll, and scroll progress indicators.
Available
Open demo →Practice delayed messages, loading spinners, dynamic lists, enabled buttons, retry flows, disappearing elements, countdowns, and asynchronous UI behavior.
Available
Open demo →Level 3
More advanced scenarios for handling complex DOM structures and automation edge cases.
Practice parent, child, ancestor, descendant, following-sibling, and preceding-sibling selectors.
Planned
Coming soon
Practice native alerts, confirmation dialogs, custom modals, and modal validation.
Planned
Coming soon
Practice dragging cards, sorting lists, moving items, and validating final positions.
Planned
Coming soon
Practice hover menus, tooltip content, hidden actions, and hover-triggered states.
Planned
Coming soon
Practice charts, metrics, cards, status widgets, filters, and dashboard validation.
Planned
Coming soon
Practice API request scenarios, response validation, status codes, and test data usage.
Planned
Coming soon
Practice locating and validating elements inside Shadow DOM components.
Planned
Coming soon
Level 4
Full practice applications that simulate real business flows from login to final confirmation.
Practice login, product search, filters, cart, checkout, and order confirmation.
Planned
Coming soon
Practice destination search, package selection, booking forms, and reservation confirmation.
Planned
Coming soon
Practice search, filters, sorting, item details, and state validation across a realistic catalog.
Planned
Coming soon
Practice availability search, date selection, user details, and booking confirmation.
Planned
Coming soon
Practice admin login, table management, filters, status changes, and data validation.
Planned
Coming soon
Practice ticket creation, priority changes, comments, status updates, and resolution flows.
Planned
Coming soon
Supported Tools
Automation Rules
Roadmap
Phase 1
Create and deploy the first public QA Labs landing page.
Phase 2
Build Login, Forms, and Tables demos with stable selectors.
Phase 3
Connect the frontend to the future QA Labs API.
Phase 4
Add examples with Selenium, Cypress, Playwright, and Robot Framework.
Status
The QA Labs frontend has started with Next.js, TypeScript, and Tailwind CSS. The first goal is to publish the landing page to labs.azealabs.com, then build the first demo pages.