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 …
The reason for choosing this product was because it works compatibly with the Microsoft product family. In addition, the widespread availability of corporate Technical Support Services also allows you to solve your problems in a shorter time. According to the open source test …
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
Verified User
Engineer
Chose Visual Studio Test Professional
I believe the thing that makes Visual Studio a solid choice is the integration with Azure and Microsoft. Apart from that, there are several open-source software available which pretty much do the same on the same scale as well.
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.
Visual Studio Test Professional is best for .NET and C# based development, which is what 90% of our developers and projects do. It is an integral part of the CI/CD pipeline for our custom made Enterprise resource planning tool. It also works very well with Azure providing seamless integration to way more functionality.
Visual Studio Test Professional when paired with Azure DevOps is the best solution for Test Case Management when compared to other Testing tools we've used in the past.
Test Results and Artifacts are always available with full traceablility for audits.
Testing and Release Management are tied together as one continuous pipeline.
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.
The user community of the Visual Studio Test product is weak. For instant problems with this product, it is necessary to quickly reach the source of the error.
Licence fees need to be more reasonable. License prices need to be reduced so that they can easily compete with free testing tools.
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.
Visual Studio Test Professional's overall usability is extremely high quality. It is extremely functional and like all Microsoft products has a user interface that is well designed and is extremely user friendly. Any functionality which I looked for, I was able to either understand immediately or find a user guide online.
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.
My team has always been able to troubleshoot with the help of customer support (and even schedule a virtual meeting!) in a timely manner. The support is provided immediately and with the necessary knowledge to answer/solve any questions/problems I or my team experience.
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.
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.
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
One of the positive ROIs of Visual Studios is the fact that it makes producing our work at a quick rate, things like Intellisense make our work get produced at a much higher rate which is good for our return of investment.
Testing by the developers has increased by 23%, we now take the time to actually test our product before we send it to our QA people.
I am not aware of any negative ROI aspects to our company that have been found.
