Visual Studio Test Professional Reviews

It's great for the development of .NET.

The solution should be cheaper. But unfortunately, Microsoft products are usually expensive.

We've been using this solution for several years and have used Visual Studio 10, 12 and 13. We use it both as a cloud solution and on-premises.

It is a stable solution.

It is a scalable solution. It is secure because most of our applications are in .NET.

The deployment was not complicated, and our developers completed the deployment. Only those two developers use the solution, and we don't plan to increase usage at this time.

Visual Studio Test Professional has an annual license.

I rate this solution a ten out of ten. I recommend Visual Studio Test Professional, primarily if you work with .NET. If we are developing something in .NET or C++, we use Visual Studio. But if we are developing something in Java, we have to use Java.

We primarily use the solution as a build environment.

The solution offers good memory analysis.

The solution has a lot of features on offer. We have not even utilized 100% features we used to use. From Visual Studio 6.0 onwards, the newer versions have a lot of features- including a built-in code analyzer - and all of that which would be very useful for us.

The solution can integrate with other solutions. In the past, we used to have BoundsChecker integrated with the solution for memory leak detection. 

The initial setup was pretty easy.

The stability has always been very good.

While I haven't used the feature, my understanding is that there are code-sharing capabilities among the developers in order to allow them to effectively review the code.

In Visual Studio we still don't have anything which can pinpoint memory leaks on a certain code line. It gives me memory analysis, however, it's not taking me to the code lines. That's what I was searching for in Micro Focus. If I could find a product that works exactly like BoundsChecker or better, then I would switch to that.

I've used the solution for a very long time. I've used it since version 1.5. It's been many years.

We've never questioned the stability. It's always been quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

We've never contacted technical support. There was never any need to do so. Therefore, I can't speak to how knowledgeable or responsive they are. 

Many years back not now, very early 2006 or 2007 or around there, we were using a product called BoundsChecker and that time we were using it very extensively and it was a very, very useful tool. We had it integrated with Visual Studio 6.0. Now, we are using Visual Studio 2017 and 2019. However, unfortunately, we haven't found any tool that gives us the same kind of output as BoundsChecker used to. When I searched its history I found that it has been bought by Micro Focus and it has changed names a lot of times. I've been looking for a product giving the same output as BoundsChecker.

The initial setup was not complex or difficult. It was easy and pretty straightforward.

We aren't bothered by the pricing of the solution at all due to the fact that it provides us with a lot of great tools. The pricing is high, however, it's a single tool that allows you to do a lot of development without having to buy multiple other tools to do the same tasks.

We're into software development. We are developing products, enterprise-level products, for clients. Microsoft is a business partner.

I'm into product management. My developers are the ones that are directly working with Visual Studio. I myself I'm not overly technical. Therefore, my insight is slightly limited. 

We are using versions from both 2017 and 2019. It might be Visual Studio version 6.0. 

We are not using a lot of it due to the fact that ours is a legacy code written back in the 1990s. It's a system library. We simply use it to build and compile and that's it.

I'd rate the solution at a nine out of ten. I haven't completely explored the whole solution, however, I've been very pleased with its overall capabilities. 

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.

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.

I am using Visual Studio Test Professional for developing architectural designs and diagnostics in the cloud.

What I like most about Visual Studio Test Professional is the way people publish templates and publish integration.

Visual Studio Test Professional could improve by having better integration with external databases.

I have been using Visual Studio Test Professional for approximately four years.

Visual Studio Test Professional is stable. It has high availability.

I have not contacted support.

The installation was straightforward for Visual Studio Test Professional.

We pay for the solution annually and the price could be reduced.

I 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.

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.