Azure DevOps Services vs. Visual Studio Test Professional

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

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.

Incentivized

• Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
• Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
• Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.

Incentivized

• Test scenarios in the SDLC process can be easily applied to the Visual Studio Test tool.
• It works compatible with Microsoft Windows Server and database.
• The debug screen of the Visual Studio Test product is quite successful. It allows you to quickly access the details of the error received.

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• 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.
• The service right now is far too expensive. You need to pay per user.
• The tools for unit testing can be improved, giving a better ability to manage tests.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

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.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

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.

Incentivized

Was not part of the process.

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

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.

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

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

Incentivized