HTML Elements Playground

Register

Practice automation testing with 50+ interactive HTML elements

1. Text Inputs

2. Buttons

3. Radio Buttons

4. Checkboxes

5. Dropdowns & Select Elements

6. Other Input Types

7. Modals & Alerts

8. Data Table

IDNamePriceStockStatus
1Product A$99.9950Active
2Product B$149.9930Active
3Product C$79.990Out of Stock
4Product D$199.9915Active

9. Tabs

Tab 1 Content

This is the content for the first tab. Test tab switching here.

10. Accordion

11. Links & Navigation

12. Loading States

13. Badges & Labels

PrimarySuccessWarningDangerInfo

14. Contact Form Modal

15. Multi-Step Purchase Order Form

16. Advanced DataTable (100 rows)

17. Basic Authentication

Username: admin | Password: admin

Go to Admin Area

18. iFrame Example

19. Geolocation API

20. Hover Tooltips

This is a tooltip!
Additional information appears here
Hover for details
You can test hover interactions with automation tools like Selenium or Playwright

21. New Tab Form

Open Form in New Tab

22. Secure Download & Upload

Download CSV

Upload Simulation

23. Flakiness Purchase Form

This section is designed for test flakiness scenarios. Submitting the form may succeed fast, may take more than 5 seconds, may take up to 15 seconds, or may fail with simulated network issues, database connection errors, or external provider errors. It also validates basic form rules and, on success, returns an invoice confirmation.

Trigger a specific scenario

Use these buttons to force a scenario. This helps you identify data test ids and validate visibility rules. While a scenario runs, other triggers are disabled. When it finishes, everything is enabled again.

ReproducibilitySeed: loading...
Reproducibility means you can repeat the same flaky sequence of delays and outcomes using the same seed. Reset rng restarts the random generator to the beginning of the sequence for the current seed, so the next run produces the same timings and results again.
Elapsed0s

Purchase Data

Flakiness scenarios covered

  • Success response in about 1 to 4 seconds
  • Slow response that may take more than 5 seconds and up to 15 seconds
  • Network issue simulation with retry needed
  • Database connection error simulation
  • External provider confirmation error simulation

Expected behavior for automation

This scenario is meant to validate robust waits, retries, and error handling. A test may pass in one run and fail in another if it uses unstable waits or assumes immediate confirmation.

Recommended checks include: validation errors, toast visibility by type, slow submission warning, and invoice modal confirmation.

Side note: The same action may complete quickly, may take longer than 5 seconds, may take up to 15 seconds, or may fail. This is intentional for flakiness testing and stability improvements.