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…
$0
Selenium
Score 8.3 out of 10
N/A
Selenium is open source software for browser automation, primarily used for functional, load, or performance testing of applications.
N/A
Tricentis Testim
Score 8.0 out of 10
N/A
Testim.io, from Tricentis since the February 2022 acquisition, leverages machine learning for the authoring, execution and maintenance of automated test cases. Testim uses dynamic locators and learns with every execution. It is designed to produce fast authoring and stable tests that learn, thus eliminating the need to continually maintain tests with every code change.
$30,000
per year
Pricing
Playwright
Selenium
Tricentis Testim
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Playwright
Selenium
Tricentis Testim
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Playwright
Selenium
Tricentis Testim
Considered Multiple Products
Playwright
Verified User
Engineer
Chose Playwright
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 …
The excel integration was key for using Selenium. I needed to be able to pull excel reports and use SQL, so I needed to find a program that would work with Excel natively. Selenium allowed me to reuse some of my existing SQL code and add a level of automation that I was not …
Tricentis Testim provides features like Codeless Automation, Rapid Test creation, Self healing tests, parallel test execution which Selenium lacks. Secondly Tricentis has reduced maintenance and ease of adoption.
We evaluated several other products, and what gave Tricentis Testim the edge was the ease of use, the customer support and the pricing. While others seemed to have a bit more complex functionality, we have been able to build almost every use case the way we would expect, with …
Testim is more easy to use than tosca. maintaining scripts easily with AI integrated feature gives a upper hand to Testim than tosca. Also less coding skill is required for Testim than tosca.
Features
Playwright
Selenium
Tricentis Testim
Automation Testing
Comparison of Automation Testing features of Product A and Product B
Playwright is very well suited for any kind of frontend QA regression testing. It's perfect for ensuring that important features that are not often updated remain fully functional across updates or releases. It is not well suited for testing a feature that requires more developer updates before it is ready for end users. Playwright tests are not always simple to maintain if frequent updates are required to keep them relevant. Playwright can be used for API or database assertions as well, but it's not necessarily best suited for those scenarios. It does perform well enough to consider that use case for simplicity if Playwright is already relevant for any frontend QA regression tests that are needed.
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.
Testim has been great at automating Frontend and integration regression testing. I do not think it would work wellTricentis Testimfor backend code testing, if it could not be done through UI. The record function is very good, and makes automating test cases much faster and more accurate. We have had great success using Testim to verify SalesForce environments, NetSuite environments, and our own JumpCloud application as well.
It provides a codeless testing environment, allowing non-technical users such as business analysts and testers to create and maintain automated tests without writing code. This democratizes test automation and accelerates test creation.
The platform leverages artificial intelligence (AI) and machine learning (ML) algorithms to analyze user interactions with the application and automatically generate test scripts. This significantly reduces the time and effort required to create test cases.
Its AI capabilities enable tests to adapt to changes in the application's user interface (UI) automatically. If UI elements change, the platform can identify and update the tests accordingly, reducing maintenance overhead.
Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.
Providing more comprehensive reporting and analytics capabilities, including customizable dashboards and insights into test execution results, could help users gain deeper insights into their test coverage and quality.
Expanding integration capabilities with a wider range of external systems, tools, and test management platforms could increase flexibility and interoperability within the testing ecosystem.
Enhancements in organizing and managing test scenarios and test suites could improve the user experience. Features such as better folder structures, tags, and hierarchical organization could make it easier to manage large test suites.
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.
This is one of the most intuitive tools, while also having the capability to do complex test scenarios. There are very few things we are unable to test with this tool. The support is also very quick and very helpful.
I find Playwright very intuitive and generally do not have any trouble using it on a daily basis. However, I do have coworkers with more limited experience in software who have struggled immensely in learning to use Playwright properly. Playwright is very well documented which helps if you plan to use AI to help you write any test automation (which I generally don't recommend, but is an option).
For those who are unfamiliar with coding, there is a bit of a learning curve. There is plenty of helpful documentation and resources but it can take a little time to get the software up and running. Once you get the hang of how Selenium works, and what it can do, you realize how many things you can use it for, and how many processes you can automate.
While the users do have some small amount of coding background, this tool does not require much prior knowledge to get off the ground. In order to do some of the more complicated test scenarios, there is a learning curve, but overall the re-usability and ease of use is fantastic.
The Selenium app has a pretty fat community of users. For the problems we are experiencing, we are primarily receiving support from these communities. In addition, there is widespread service support. Instant support is given to the problems we experience when we need Online support. We and our team are happy to provide this support, especially before important deployment processes
The customer support is the best I have ever experienced, both personally and in a job role. The chat anytime is a very nice option, there has never been more than a few minute wait to connect with someone, and the agents are very knowledgeable and helpful.
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.
We evaluated several other products, and what gave Tricentis Testim the edge was the ease of use, the customer support and the pricing. While others seemed to have a bit more complex functionality, we have been able to build almost every use case the way we would expect, with very few workarounds.
