Visual Studio Test Professional Reviews

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 am using Visual Studio Code. Currently, Visual Studio is used for testing code, including unit testing. For Azure orchestration, we use GitLab.

The integrated unit testing and extensive search features have made things easier.

The unit testing is integrated with Git. Searching is extensive and helpful.

The Git extensions are very basic and can be more extensive compared to other software focused on Git, like GitTower or SmartGit.

It's been six months since I last used Visual Studio. Recently, I haven't faced any issues.

No instability issues are mentioned.

No scalability issues are mentioned.

I have not used customer support, so I cannot comment on it.

We used Zoom for communication. I have not used it for a long time now. We have moved to using Teams.

The IT department handles certain aspects, and I am not informed about them.

GitHub Copilot hasn't been started yet, and Visual Studio Test Professional is used for testing.

I'd rate the solution seven out of ten.

The product is primarily used for integration with other products and applications, facilitating the exchange of information between old and new applications.

The tool is flexible and easy to manage. We use it since it is scalable and easy to use. It integrates with solutions. 

Visual Studio Test Professional needs to improve its stability. 

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

I rate the product's scalability a seven to nine out of ten. 

Visual Studio Test Professional's deployment is not complex. 

Our larger organization has three organizations that are directly involved in working with the product. One organization focuses on security, while another is engaged in software development, particularly creating interfaces, software links, and product integrations. I rate it a seven out of ten. 

We are primarily using Visual Studio Test Professional for the C Sharp environment.

It is a good and user-friendly tool.

The product is only available on Windows. It could be available for multiple platforms and other operating systems like Mac with a native port. It is challenging to use it for larger projects. Also, it needs to be rewritten with additional features.

We have been using Visual Studio Test Professional for more than twenty years.

It is a very robust and stable product.

The product needs to be more scalable. It requires a good set of machines to perform well.

The initial setup process is long and tedious. It works like installing an operating system on the server and takes an hour to complete. We run the setup, select the components and features, and install it on the system. It is well organized but a very lengthy process.

I installed the product myself.

The product generates very low revenues for us.

We have licensing for Visual Studio Community edition.

I would not recommend Visual Studio Test Professional. I rate it an eight 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 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. 

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.