Progress Test Studio aims to be the easiest to use Web Automation tool on the market, widely used by Enterprise
QA’s for testing, but easy enough for anyone.
The product automates testing for WPF,
Silverlight, Web, HTML, Angular, React, KUIB, iOS, Android, Mobile Web, and
API’s.
Test Studio is ideal
for a no-code or low-code approach for: QA Test Automation, Application
Monitoring, Performance and Load Testing, Web/Marketing Process Automation, and
Mobile App Automation.
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.
N/A
Pricing
Progress Test Studio
Selenium
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Progress Test Studio
Selenium
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Progress Test Studio
Selenium
Considered Both Products
Progress Test Studio
Verified User
Anonymous
Chose Progress Test Studio
We did not use any other product for test automation prior to this we used to do manual testing.
Test Studios had a smaller foot print and allowed us to ease into deploying it in the company. The online help was a great benefit to getting started and the evaluation period allowed us to fully run though the product before purchasing it. Cost difference between the …
Very easy to record both http/https pages and supports all major browsers. Test Element repository is the killer feature that gives you piece of mind and confidence to write and reuse elements for several different scenarios. The built-in testing framework which also includes …
Testing features between the different tools we evaluated seemed to be fairly equal but the user interface, using other products within the Progress suite of products, and the cost of Test Studio lead us to our decision.
When we compared Selenium to Saucelabs, [we found that] both have their own set of advantages but [preferred] Selenium [in the end]. [With] Selenium we have a uniform setup in place to test both the framework and grid which makes it preferable over Saucelabs. [The] test …
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 …
Customers are always spending less cost on tools and prefer open-source tools which leverage all applications Can be tailored your framework in selenium according to application Moreover CI/CD pipeline is easy in selenium compared to other tools Can be built custom test …
The main Selenium usage is in the security field. Selenium drives the web application and let ZAP test some piece of software and UI in order to find security issues. Is Jenkins in charge to run it and manage reports? For the reporting, we tried many solutions, including …
Open sourced and free: Multiple language support: The community: Wide plugin support: Easy installation and intuitive usage: Cross-browser support: Remote testing: Multiple testing and parallel testing execution:
The main reason I prefer Selenium is because it has a fairly common user community and because it 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 …
Since it is an open-source testing tool, there is no licensing cost involved. Selenium is a cross-platform tool that supports cross-browser testing. To manage and report test cases Selenium can be easily integrated with frameworks like JUnit, TestNG.
We have looked at other options, but none are open source like Selenium and easily plug able into different web applications. Selenium does not cost anything, and although you don't get support for it, there are many technical forums our there that provide troubleshooting if …
The first obvious thing is Selenium, an open-source tool, and it has a wide-open community for support. Well, on the other hand, Silk Test is a paid tool. With the combination of different tools in the market, we can build a solution for Web and Mobile based automation using …
UFT is a paid tool from microfocus and able to automated alomsts all platforms but there is Fee for licensed versions software. TOSCA is also a paid tool from Tricentis which does not require coding skills from tester and implements mode based automation. where as selenium is …
TestComplete is more like an enterprise automation testing tool, that consists of many built-in functions. The license is rather expensive https://smartbear.com/product/testcomplete/pricing/. TestComplete's user community is not as large as Selenium user. Smartbear's …
We use both the products in our work. Mostly we avoid Selenium because we have replaced that half of the work with RPA, which works faster than Selenium and with less brainstorming. Some of our work can only be done with Selenium, while some of our work can work faster with RPA.
All alternatives are not listed here (like QTP), but Selenium beats all of them because it's free, there are tons of guides and tutorials on the internet, and there are lots of extra libraries that use Selenium.
We were considering HP QTP against Selenium. but we chose Selenium because of the following reasons: 1. Selenium is more widely used and has more online support community
Ghost Inspector, a cloud-based automated web app testing tool, used for recording and playback, a lot like Selenium IDE. Ghost Inspector provides Google Chrome and Firefox plugins to record browser actions and allows users to save the tests on their cloud platform. It allows …
The product is easy to learn and any customer making web based application will greatly benefit from a product like this and cut down on testing time. As new code builds go out it's an excellent tool for regression testing. The load testing feature has a great benefit as well and lets us test the limits of the application on different platforms and allows us to tweak the certain area and test again.
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.
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.
Very easy to record both http/https pages and supports all major browsers. Test Element repository is the killer feature that gives you piece of mind and confidence to write and reuse elements for several different scenarios. The built-in testing framework which also includes the .NET Framework Library. Integration with Jira. Supports source control such as GIT and Team Foundation.
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.