Visual Studio Test Professional Reviews

When using Visual Studio, we have two type types of reports that we use including TFS and Git. I use TFS to open the solutions, make any changes and to complete tests for quality program production.

The most valuable feature has been to store all our packages in one place including SSIS packages, SQL tables, TFS and SSR.

The server that we use is very slow so that is concerning for us.

We have been using this solution for almost a year.

This solution is not that stable. The server that we use is very slow so that is concerning for us.

This solution is scalable. 

We have our own tech support in the office so we do not use their customer support.

The initial setup is straightforward. We have partial scripts and we used them to run the setup using Octopus.

I would advise others to save changes in their repository or it might get lost.

I would rate this solution 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.

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.

I use Visual Studio Test Professional to review codes to ensure developers maintain the coding standard procedures and standard security while writing the codes. There is a platform on DevOps that enables developers to review their codes.

Visual Studio Test Professional is a scalable solution.

Visual Studio Test Professional should include more automation.

I rate Visual Studio Test Professional a nine out of ten for stability.

The solution’s initial setup is straightforward.

The solution's deployment time depends on the version. We use the community version in our office, which pulls data from the internet to install. So, you can deploy the solution in less than ten minutes if you have a fast internet connection.

We use the solution’s community version, and the solution’s pricing could be cheaper.

I would recommend Visual Studio Test Professional to other users.

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

I use the solution for web-based application development.

The solution has good stability.

The solution's UI could be better.

I have used the solution for a month or two.

It is a stable solution.

It is a scalable solution.

The solution's initial setup process is easy.

I implemented the solution myself.

I rate the solution a six out of ten.

It helps us to create happy and safe solutions.

It is a free solution, the documentation is easy, and it helps us solve our problems.

It is hard to learn, and you need to invest time to understand it. The interface could also be more simple.

We have been using this solution for four years. It is deployed on-premises and on Azure cloud.

It is a stable solution.

It is very scalable. The backend developer and full-start developer use this solution, and it doesn't require maintenance.

Few people are needed for deployment, and it is easy because it is Microsoft technology. It takes about one hour to deploy.

I rate this solution a nine out of ten. I would recommend this solution to others, but it requires a lot of learning to use it.

We do a lot of test-driven development and acceptance test-driven development, so we write all our test cases for our .net development through Visual Studio Test Professional. 

Visual Studio Test Professional has allowed us to increase the quality of one of our web portal products drastically. We went two years with only one regression in our software because of the automated testing we built with Visual Studio Test. 

Visual Studio Test Professional's most valuable feature is the rich IDE for doing code and test development.

I've been using Visual Studio Test Professional for as long as I can remember.

I'd rate Visual Studio Test Professional's stability eight out of ten.

I would rate Visual Studio Test Professional's scalability nine out of ten.

The initial setup was pretty straightforward.

We've seen an ROI because the IDE is much richer than others we've used.

Visual Studio Test Professional is a little pricey - I would rate its pricing six out of ten.

I would recommend anybody thinking of implementing Visual Studio Test Professional to go for it. I'd give Visual Studio Test Professional a rating of eight out of ten.

We use it for the the developing web applications than web services Test applications.

It has some of the best documentation in the world.

There are some stability users that needs to be bettered.

I have been using Visual Studio Test Professional since the mid-eighties.

It is a stable solution.

It is a scalable solution. Only five users are using a solution.

One of the best technical support team.

The initial setup is easy.

There is a Return on Investment.

It is a price-effective solution.

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