Why use demo sites for test automation
Before you spend time learning and building a test suite for a new automation framework, it's a good idea to try it out on different types of websites to make sure the framework works reliably and is easy to work with. For example, if you are currently using Selenium but want to try Cypress, Nightwatch, WebDriverIO, or Playwright, try doing more than a simple example on these sites. This way, you don't have to find that your chosen automation framework isn't working in some critical area for which you need to write automation.
Most likely, you will want to try out your test automation framework on objects such as:
iFrames
Modal windows
New tabs
Multiple windows
Asynchronous content loading
File upload dialogs
. , , .
-, , . , .
"The-internet" Github
GitHub , ; , (shadow DOM), .
- The Automation Practice. automationpractice.com
, Selenium. , .
ToolsQA. demoqa.com
DOM, , .
UI. uitestingplayground.com
, , , , - .
SwagLabs. saucedemo.com
, . , 4 , ; , , . SauceLabs.
GlobalsQA
- , Angular. , , .
REST API
SuperTest + Mocha API Postman, .
Swagger Petstore. petstore.swagger.io
API. Swagger REST API, , , API .
Restful Booker. restful-booker.herokuapp.com
Test all kinds of CRUD (Create, Read, Update, Delete) REST API scripts using this API booking site.
If you know about any other good sites, share them with everyone in the comments.
Translated by the QApedia team . Subscribe to our channel.