Visual Studio Test Professional Reviews

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.

The interface is easy to use.

The designs are not really very appealing. When you make the design, it's quite basic which includes the icons. The tool needs to include brighter colors and be more user-friendly. The interface should be made attractive.

I have been using the solution for two years.

The product is stable. 

It is a scalable solution. There are five to ten users presently.

I think the technical staff are well-versed because they usually have to make designs for the customers.

The initial setup is easy. For me to start the design from scratch, it actually took less than 15-30 minutes.

I rate the solution a seven out of ten.

Visual Studio is an IDE that we use for development.

Visual Studio is the easiest to use. 

We have used Visual Studio for as long as I can remember. It has been about 10 years.

I rate Visual Studio nine out of 10 for stability.

I rate Visual Studio nine out of 10 for scalability.

Setting up Visual Studio is straightforward, and it takes a couple of hours at most. 

They have different pricing levels. There is a free community edition, professional, etc. It depends on the use. The price is reasonable, but it's not the best.

I rate Visual Studio Test Professional nine out of 10. I highly recommend Visual Studio for any software engineer.

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.

Visual Studio Test Professional is purely used for the development of web applications, Windows services, and API.

Visual Studio Test Professional is a complete IDE. The most valuable features of Visual Studio Test Professional are the IntelliSense and the ease of adding the NuGet packages.

Sometimes, the solution hangs, so its performance could be improved.

I have worked for different organizations and have been using Visual Studio Test Professional since 2010.

Visual Studio Test Professional is a stable solution.

Around 50 users are using Visual Studio Test Professional in our organization.

The solution's technical support is good, and we have no complaints.

The solution's initial setup is straightforward for me because I have been using it for quite some time.

We implemented the solution through an in-house team.

We have seen a return on investment with Visual Studio Test Professional because it improves developers' efficiency.

Our company pays a yearly licensing fee for Visual Studio Test Professional.

I would recommend Visual Studio Test Professional to other users.

Overall, I rate Visual Studio Test Professional a nine out of ten.

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.

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.

I use this solution to load data from Excel into a database and perform transformations on the data in between.

The most valuable features are the SSIS reports, the deployment models, and the ability to interact with other Microsoft tools.

The stability of this solution needs to be improved because sometimes it hangs and crashes.

The speed at which deployment can be done has room for improvement.

The support documentation that is available on the Microsoft website should be improved.

I would like to see more visuals, such as graphs and diagrams, added.

I have been using Visual Studio Test Professional for two years.

If it were not for the hangs and crashes that I sometimes experience, I would say that this solution is stable.

This is a scalable solution and I have enrolled a lot of users. We have perhaps 1,000 users.

I would rate Microsoft technical support for this solution a seven out of ten.

I have not spoken with them directly, but I have had problems when I go online and search for solutions. The documents on the Microsoft website are not very useful, and they ought to make it easier to find answers. The documents, overall, are a bit hard to understand and are not user-friendly. 

I have used previous versions of Microsoft Visual Test Studio including the 2010 and 2008 editions. I switched to the 2015 version because of the new features.

I would say that the initial setup is fine, although I would rate it a medium level of complexity. Deploying this solution is not very quick, which is something that can be improved.

I was also considering Alteryx but I chose this solution because of the cost.

I would rate this solution an eight out of ten.