A cross-browser testing tool, playwright supports all modern rendering engines including Chromium, WebKit, and Firefox. Users can test on Windows, Linux, and macOS, locally or on CI, headless or headed. It is also cross-language, so that the Playwright API can be used in TypeScript, JavaScript, Python, .NET, Java. Test Mobile Web. Native mobile emulation of Google Chrome for Android and Mobile Safari. The same rendering engine works on the Desktop and in the Cloud. Playright…
N/A
Selenium
Score 8.1 out of 10
N/A
Selenium is open source software for browser automation, primarily used for functional, load, or performance testing of applications.
When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.
Recognize Adobe Flash and MS Silver Light elements without additional help
Detect and locate Java applets ingredients
Having the "Wait-till-Displayed" or "Wait-till-Present" as a built in Web Driver function instead of requirement for writing loops and defining expliccit wait, visiblewait, invisiblewait, etc.
We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.
It makes automating complex user interactions easier, fits right into our CI/CD for continuous testing, and works great across different browsers. The Documentation is a plus, you don't really need to search a lot to understand and find what you need for the coding. The community is small but very helpful, which makes it a breeze to use and a must-have for keeping our software in top shape.
As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.
Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.
We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.
We selected Playwright over the rest for several reasons. The learning curve is faster, making it easier for our team to get up to speed quickly. The setup is pretty straithtforwared, minimal configurartion needed and a great example included in the configuration which includes all the basics to start writing using that spec as a placeholder. Compared to Cypress, Playwright support multiple browsers out of the box, giving us broader testing coverage. Appium is great for mobile testing, but extremely slow.
At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.
Generation of detailed finding reports helped in cost savings in regard to direct labor.
Quality Assurance technicians found value in repeating mundane duties that they perform daily. It saved mental energy due to the automation process.
The value was established in high volume usage in setting up meetings as well as new accounts with A/B testing. Also merely cleaning up old test documents by evaluating them and organization or deletion.
