Visual Studio Test Professional Reviews

Visual Studio is for custom software development.

Visual Studio is highly powerful. It's probably the best software development tool on the market.

Some of the features appreciated by our teams that work with VS are:

IntelliSense, rename functions (classes, methods, variables), move definition to file, error navigation, search in files (match case, regex), NuGet package manager, GIT experience (especially at solving merge conflicts and view history on a specific file, compare with the previous file to see changes in time), watch list and the fact it can be pinned for the variable you are monitoring, conditional breakpoints, moving execution line up when debugging, shortcuts to arrange elements in the page and remove unused namespaces, possibility to chose the Thread you want to monitor when you have multiple threads, code snippets, easy navigation to the definition and to other classes/methods/properties that refer them, and configuration of code cleanup on multiple profiles and with a lot of options.

We have been selling Visual Studio for more than 10 years.

Sometimes Visual Studio is slow. It uses a lot of resources like memory and processing power. You should optimize the performance by only installing what you need on your machine. Don't install unnecessary things that will slow your machine.

It depends on what you mean by scalability. Only one person uses Visual Studio at a time, but it's scalable in terms of project size. We have
70 users. We will grow usage as we grow the department and the company. We're expecting between 5 and 10 percent growth in usage next year.

Microsoft support could be faster. It took a while to get to a knowledgeable person in some cases, but we got the answer that we were looking for in the end.

Setting up Visual Studio is straightforward. Each developer configures their own environment.

We have both options. Some licenses are paid yearly. Others are monthly subscriptions.

I rate Visual Studio Test Professional nine out of 10.

Our primary use case of this solution is for UA automation. I'm a process manager and we are customers of Visual Studio. 

The product is very easy to use and we were able to scale up the automation solution quickly which was beneficial.

It's an expensive solution which is an issue for us. 

I've been using this solution for five years. 

The solution is stable and we get upgrades every couple of years. Most of our developers use Visual Studio; we have around 150 users in total.

The initial setup is straightforward, it took us around four to five hours and we were able to do it by ourselves with our own three-person IT team.

We pay an annual licensing fee. 

We took a look at Tricentis Tosca and SmartBear TestComplete a few months ago but nothing has been finalized. We're looking for an alternative to Visual Studio Test Professional. 

If cost is not an issue then I would recommend this solution. 

I rate this solution eight out of 10. 

I am using this solution to automate the sequencing of processes and to manage them. For example, using remote access services to see the interactions between applications. It has taken us two years to build the tool we are working on. 

The ability to quickly make your own components has been valuable. The documentation is simple but you will need to explore the solution and put in the effort for success.

One of the problems with this solution is you need to be highly technically skilled to operate it, it is not for everyone. Additionally, I would like to see an orchestrator added to the solution.

I have been using the solution for approximately 15 years.

The stability is great, I trust in the solution.

We have 20 people in my organization using the solution.

The installation of the solution is easy. However, if you want some additional components such as Workflow which is not including in the original packaging of the solution, it will take more time to install.

The solution is very powerful but you have to know how to use it.

I rate Visual Studio Test Professional an eight out of ten.

I use it for coding, debugging, and other usual things.

It is very easy to use. You can handle a lot of things together at once in one package, which is a good point for us.

It is not good in terms of performance. When you open Visual Studio, you have to wait for a while to process your code. It uses a lot of resources and has a lot of features. If we could disable some of the features, it would be lighter and faster to use. Nowadays, for some of the projects, we use VS Code for JavaScript or Python. VS Code is very light and easy to use, whereas, in Visual Studio, we have to wait because it takes time to compile or run a project. It has a lot of competitors in terms of performance, such as Intelligent ID. Intelligent ID is very easy to use. It has many features, and it is lighter to use than Visual Studio.

In terms of error handling, sometimes, it shows an error before you finish your code, which can be improved. It would be good if it has a version for Linux. I use VS Code on Linux, but I am not sure if Visual Studio has a version for Linux.

I have been using this solution for four or five years. 

I haven't contacted their technical support. We always search on the web. You can easily find most of the information on the web or Microsoft site. They have a big community, and you can find the information very easily.

The initial installation is very good and easy. In 2015, they added a visual installer, which made it easier than before. Nowadays, we use Visual Studio to change or modify some of the packages, and it is much easier than before.

I would recommend this solution. I would rate Visual Studio Test Professional a seven out of ten.

I use it just for coding our applications and features. We are using version 4.5, which is an old version. We haven't tried its latest version.  

It probably is deployed in a private cloud. It is a part of our firm architecture or infrastructure. 

It is a very common and strong product. A lot of support is available for this product.

It needs more integration with other tools for monitoring. Microsoft also needs to make it more modern to make it work with microservices and the cloud. It is a bit outdated currently. 

I have been using this solution for five years. 

It is stable. We didn't find any issues.

I don't know much about scalability. It is more related to the infrastructure side. 

We have around 2,015 people in our organization who use this solution.

I have never really used Microsoft technical support. I just find the information on the internet.

It is easy to set up. The deployment duration depends on the projects. We are working with different projects and persons. For one of our projects, we need one week to deploy. We usually test when all the teams have integrated changes in an environment. It takes some time to test. After that, the changes are deployed to another pre-production environment, where we again test. After that, when we are sure, we deploy to the production environment.

It is an old technology, and I would like to try using a new technology. However, it is necessary for us to stay with this technology because we have a legacy product, but we are thinking of updating to newer versions or migrating to another technology. We didn't do that in the past because of the fear of losing some of the features and having any kind of breakage because of incompatibility. We are looking for microservices for the database. I would advise not to keep a lot of gap between upgrades. The risks are more when you upgrade after a long gap, such as four years. It also takes more time to test all the functionalities.

I would rate Visual Studio Test Professional a seven out of ten.

There are many valuable features, including the integration between the management data and the test cases. You have the ability to link them with the requirements and user stories. You also have the ability to track the running of the test cases and the reporting of the results of each test case. You are able to send some reports via dashboard control to see the status of the overall testing across specific requirements or specific user stories. It enables us to connect the bugs and the cases to the requirements.

The service right now is far too expensive. You need to pay per user.

The solution needs more reports and more dashboards as well as more details for each originated spare test case or best guess in test cases.

There are still some issues in the results. There is an extension integrated with the test manager that enables you to run manual testing and to track the progress of any scenarios you've written in the Test Professional. We have noticed some bugs in this extension and this is the core of running the manual test cases. These bugs need to be resolved. They have to enhance or to add more stability to this extension specifically.

The solution is very stable. We didn't find any issues regarding the stability or the maintenance of the system.

The solution is very scalable. The main concern is the cost. Even if it were implemented on-premises, the cost of the license is too high. Currently, we have around 20 to 25 users, all of which are engineers. We are planning to expand this number; we need to publicize this system across the organization.

We are satisfied with technical support. Communicating with them is very simple. We also have a lot of online resources to check and to study and to train our team with. The documentation is very clear and readily available.

The initial setup was straightforward. The cloud service allows you to subscribe to use it. We also have an on-premises model and it was very simple to install and implement that as well.

We implemented the solution ourselves.

For the cloud services option, you buy a subscription per account or per user. This costs around $52 a month per person.

We are using the cloud deployment model, on Azure cloud services as well as an on-premises deployment model.

We have around 100 quality engineers that we eventually want to get on the system. To do this, we need to apply a test specific license for using and testing the modules in a real case or in TFS. I don't know how much this will ultimately cost, but it's not cheap. We are a partner with Microsoft, so we are eligible for some free license-related testing. We're using the on-premises deployment model for this. They do require some subscriptions for cloud services with limited accounts as well.

The highest value for this product is the integration. Everything is tracked, everything in your software lifecycle can be integrated. Data can be added. You can track and monitor and make some reports and dashboards across your project to get more details as well as more accurate data about day to day activities done on your project. It's very useful.

Before using Visual Studio Test Professional, we could not imagine that we could track certain types of or large amounts of data for the testing team. We were so focused on the development and issues and bugs without linking them with testing. Now we use testing data and test management to test the plans and to link everything with the requirements and the project lifecycle.

I would rate this solution nine out of ten.

As a software developer working on the Microsoft platform, I find Visual Studio Test Professional to be a valuable tool for ensuring the quality and reliability of my applications.

Visual Studio Test Pro is super helpful for my Microsoft app work. It easily works with Visual Studio, helping me find and fix bugs fast. It does both manual and automated testing, making sure my app works well.

In terms of improvement, I would appreciate some enhancements in the interface, maybe adding more color options.

.

Visual Studio Test Pro is quite stable.

It is fairly scalable.

The support is good, but it could be a bit faster.

The initial setup is fairly simple. 

It is a bit pricey.

Overall, I would rate Visual Studio Test Pro as an eight out of ten.

We use this solution to develop code.

The price could be improved.

I have been using this solution for two years.

I would rate the stability a ten out of ten.

I would rate the scalability a ten out of ten.

The initial setup is easy. It's easy to configure.

The deployment can be done in-house.

We pay for the license. The licensing model is per year. So, yearly-based license.

I would rate the pricing an eight out of ten, where ten is the most expensive and one is the cheapest.

Overall, I would rate the solution a ten out of ten. I would definitely recommend using the solution.