Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
$45
per month
Visual Studio Test Professional
Score 7.0 out of 10
N/A
Microsoft's Visual Studio Test Professional is a performance testing solution.
N/A
Pricing
Microsoft Visual Studio
Visual Studio Test Professional
Editions & Modules
Professional
$45.00
per month
Enterprise
$250.00
per month
No answers on this topic
Offerings
Pricing Offerings
Visual Studio
Visual Studio Test Professional
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft Visual Studio
Visual Studio Test Professional
Considered Both Products
Visual Studio
Verified User
Anonymous
Chose Visual Studio
For beginners, the other tools are easier to set up and run. It is also entirely customizable, but Visual Studio Code has more plugins that allow you to streamline your work.
MATLAB and QT are way more different than Visual Studio. Despite of being famous as per their IDE environment, they would not stand much comparison with VS Visual Studio IDEs. because, MATLAB and QT are limited edition and feature related Visual Studio IDEs, and they stick to …
We choose Visual Studio IDE because it is easier to set up with C# and more stable. Each time we use Eclipse to make a program, we had bad behavior. Maybe that was our computer setup but we finally go with something more stable and more useful for our company.
Visual Studio is somewhat different from LiveCode. LiveCode is a coding platform that is unique and implemented most often by colleges, universities, and other academic institutions. It is more of a coding language than a team-collaboration resource. However, the LiveCode …
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, …
It's a well [maintained], mature IDE, which has the benefit of being a [software] which only the most skilled developers works on, instead of being open source. It has a lot of very useful features, which most free IDE-s don't. Also, it has many options from commercial …
Some of the editors are suitable for a particular programming language . For example pyCharm is suited for Python .
Visual Studio has support for many languages and Visual Studio is comparatively light weight from most of the IDE . The ability to get extensions and use them is …
Eclipse, PyCharm, Netbeans I have used during my internship for smaller applications but to have a full end-to-end application with ease to connect to database and deployment I believe Visual Studio is way better than other available IDE in this space. Although your options get …
I can't compare the NetBeans or PhpStorm with Visual Studio IDE due to entirely different use. All software development IDEs holds their importance, but Visual Studio IDE is the best among its competitors--the IntelliSense and standardization of development, in particular,are …
Visual Studio IDE is on par with Rider. There are some code insights and package management that Rider does better, but it's the debugger and profiling I find more powerful in Visual Studio IDE. I also consider the UI in Visual Studio IDE to be more appealing and intuitive to …
The main reason why we can't choose the Visual Studio IDE is that the entity framework provides excellent solutions. Besides, there is a very strong community of users. The Visual Studio IDE has a very user-friendly display. Creating functions and creating classes is much more …
While I mentioned that Visual Studio IDE could be slow, it isn't as slow as Eclipse by any stretch. While Eclipse is free, time is money, so take your pick. I once picked up JetBrains as I heard some good stuff about it, but it felt really buggy. It wasn't worth veering away …
Visual Studio was my preferred IDE before Rider became mature enough to replace it. Rider's performance, source control tools, and built-in refactoring make VS limited to specific use cases where Rider doesn't support.
While I am not a Java developer, I have used NetBeans in the past. I found the NetBeans interface to be more intuitive than the Visual Studio IDE. However, it was also more limited in scope. VS Code, on the other hand, is simplicity itself. It is excellent as just a text …
Visual Studio IDE is a much more comprehensive package with a lot of libraries that come out-of-the-package, compared to its rivals/alternatives who have some specialization and niche areas. Due to this nature, it is possible to develop any kind of software, using almost all …
Visual Studio Code is a very nice lightweight IDE (if you can call it that), that can be used at types of business (small to large). However, since you have to trust the sources of your plugins it can be a little more nerve-wracking at larger businesses to use this tool. Also, …
Visual Studio Code and Visual Studio are both great tools. VS Code is much "lighter" and therefore faster when opening solutions. So I tend to use both depending on the use case. If I'm developing a spa app or just want to open a solution for review I'll use VS Code. If I …
No added value. If Visual Studio costs too much then I see the point. But otherwise there is just no need for any other tool. IntelliJ is a mess, buggy and counter intuitive. Or maybe it's because java is not a particularly cool language...
Compared to a lot of these options (which are free except WebStorm), Visual Studio definitely leads the pack as far as its completeness of feature set. There are deep integrations with the Microsoft ecosystem with Visual Studio that the others can't really compete with, as …
I work mostly in C++ so CLion from Jetbrains is a nice alternative...but it just doesn't stack up to Visual Studio. My paid version of VS meets all of my development needs and has done so for more than two decades so I see no reason to look any further. That said, I have looked …
When using Azure Devops, it only has a basic test plan while using the extension, and it is better suited if you only use Azure Devops, but VS test professional provides comprehended test execution and management as most of the developers and testers use Visual Studio to …
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
Visual Studio Test Pro is well ahead of the competition due to its integrations and consolidation of tools and capabilities in one place. It offers the entire life cycle capabilities for development, testing, and deployment. The cloud offering with Azure integration makes it …
The reason for choosing this product was because it works compatibly with the Microsoft product family. In addition, the widespread availability of corporate Technical Support Services also allows you to solve your problems in a shorter time. According to the open source test …
Visual Studio Test Professional is a significantly better program than JMeter because although they are both quality programs, the integration of Visual Studio Test Professional with Visual Studio allows for easier user experience. Further, as we already use Visual Studio to …
Eclipse is great for Linux users, and it's considered more "lightweight" (less memory usage) in comparison to the "heavier" Visual Studio (more memory usage). Eclipse has a great auto-finish capability used when writing code. OutSystems is great to use when writing for mobile …
Our dev team is used to developing with Microsoft tools and managing projects with Azure devops server and service. QA uses the same collaborative platform, so it was easier - almost natural - for all of them to use Visual Studio Test Professional, with full integration and …
Visual Studio Test Professional is head and shoulders above the other options we've tested and used in the past. Our Legacy teams were still using Quality Center as of a month ago and they just switched over to Microsoft Test Professional to join the rest of the organization …
I believe the thing that makes Visual Studio a solid choice is the integration with Azure and Microsoft. Apart from that, there are several open-source software available which pretty much do the same on the same scale as well.
We did not evaluate other options. This solution was released while we were using third-party tools, and once that happened we knew that we had to use it because of the integration.
Visual Studio IDE has a lot of test functions to developers. The Enterprise Version allows installation of full test manager features. It is best if you have a Microsoft Enterprise Agreement. Visual Studio Team System or Microsoft TFS incorporate a lot of test management …
Test Professional is a much more rounded product by nature of its integration with Team foundation server. Much lower administrative effort required as only one system needs to be hosted.
Being in college I have used a lot of less developed software. Visual Studios offers a wider variety of tools that helps find where the problems in our software are along with editing options that make these changes less painful and way easier to accomplish. Before we used two …
It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.
Visual Studio Test Professional is best for .NET and C# based development, which is what 90% of our developers and projects do. It is an integral part of the CI/CD pipeline for our custom made Enterprise resource planning tool. It also works very well with Azure providing seamless integration to way more functionality.
Rock solid intellisense. For C# and VB.Net code, the intellisense provided by Visual Studio is hands down the best. If you find that you have a hard time remembering parameters of functions, or what object names were, the intellisense will rescue you and help me be an efficient developer.
Super fast and simple to use debugger for C# and VB. Everything in the debugger is handed to you on a silver platter. When you stop on a break point, it immediately shows you the local variables, the call stack, and even your current memory usage. Setting up watch variables is super simple and you can even make breakpoints conditional so it will only stop on certain conditions.
Hides the tedious tasks. There are quite a few things like publishing, creating click once deployments, and adding/removing settings in the project files that can be really time consuming when trying to do it by hand (such as if you don't have access to Visual Studio and you need to make changes). Visual Studio hides all the tedium from you by making nice point and click interfaces to get things done quickly.
Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.
Visual Studio Test Professional's overall usability is extremely high quality. It is extremely functional and like all Microsoft products has a user interface that is well designed and is extremely user friendly. Any functionality which I looked for, I was able to either understand immediately or find a user guide online.
Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.
My team has always been able to troubleshoot with the help of customer support (and even schedule a virtual meeting!) in a timely manner. The support is provided immediately and with the necessary knowledge to answer/solve any questions/problems I or my team experience.
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
When using Azure Devops, it only has a basic test plan while using the extension, and it is better suited if you only use Azure Devops, but VS test professional provides comprehended test execution and management as most of the developers and testers use Visual Studio to develop their apps and publish their builds.
Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.
Visual Studio Test professional fits right in with the other Microsoft Lifecycle Management tools.
End to end, Development, Test, Deployment and Delivery assures the pipeline is continuous. Visual Studio Test Professional is an integral part of that pipeline.
Familiarity with Microsoft Tools makes usability intuitive, makes it easy to ramp up our Testers.