Try our new research platform with insights from 80,000+ expert users

Microsoft Azure DevOps vs PractiTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 15, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Azure DevOps
Ranking in Application Lifecycle Management (ALM) Suites
2nd
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
135
Ranking in other categories
Release Automation (1st), Enterprise Agile Planning Tools (1st)
PractiTest
Ranking in Application Lifecycle Management (ALM) Suites
21st
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Test Management Tools (18th)
 

Mindshare comparison

As of September 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Microsoft Azure DevOps is 13.0%, down from 22.8% compared to the previous year. The mindshare of PractiTest is 0.8%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites Market Share Distribution
ProductMarket Share (%)
Microsoft Azure DevOps13.0%
PractiTest0.8%
Other86.2%
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Ivan Angelov - PeerSpot reviewer
Facilitates agile transformation with potential for enhanced intuitiveness
What I liked about the solution is that it offers numerous features that are not available by default unless you are agile. Transitioning from the traditional Waterfall model to an agile methodology was challenging for us. Until 2020, our team predominantly worked with the Waterfall approach, using local tools like ServiceNow. We had a few team members who were familiar with Agile ISO, but none had experience with Azure. Therefore, we pursued Azure certification at the AZ-900 level. Our company organized a training session with a certified Azure expert, which was extremely beneficial for adopting best practices during the initial three months. This preparation helped us get accustomed to the new tool, as transitioning to a new system invariably requires time. Managing a pipeline of deliverables became significantly easier with this solution. We utilized it for stories and integrated change management with Azure DevOps. Eventually, everything related to the environment was organized there, enabling us to follow up and track progress with our technical engineers on an hourly, daily, or weekly basis. Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap.
DC
Flexible and intuitive with easy reporting, and good support that is instantly available through chat
It doesn't allow you to connect to multiple different bug tracking tools at the same time. This is not an issue if you only have one bug tracker but we can potentially use different tools for different projects. As an example, if you connect PractiTest to Jira for one project, that's the one you have to use for all projects. We had a requirement to connect with Jira for one project, and a different tool for another, project but it was unable to accommodate that unfortunately. I would therefore like to see it easier to integrate with bug tracking tools at project level which would give each project the opportunity to use a different bug tracker if required.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It is easy to use. The shared repository is useful. Everything is in one environment."
"Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support."
"The pricing seems to be reasonable."
"The simplicity is very good and the customer experience is also great."
"Overall, so far we have no major issues to report."
"It's a pretty problem-free solution."
"The features that have a significant impact on us include CI/CD, where we have full integration with the source code repository and Azure Pipelines."
"Microsoft Azure DevOps has helped the developers a lot and we are deploying process changes very frequently and simultaneously. A lot of my team members that are developers are updating the code in parallel using Git. Additionally, Microsoft Azure DevOps is providing a very good approval mechanism. Overall it is benefiting by creating efficiency in production deployment and applications, our new releases are running well. The security of secured is good."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
 

Cons

"Azure has not yet advanced to the performance level of the other major competitors and is missing integration with important technologies."
"This product would be improved if the helpdesk were included."
"When converting to DevOps, it was difficult to map."
"Improving the metrics that are readily available on the dashboard would be very helpful."
"The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow."
"They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server. I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script."
"The initial three months were particularly challenging, and without the help of an external consultant, adapting to the change in work processes would have been difficult."
"There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps."
"It doesn't allow you to connect to multiple different tracking tools."
 

Pricing and Cost Advice

"The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves."
"It is the least expensive product in this class."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"Compared to other tools, Microsoft Azure DevOps is a cheap solution."
"It has an annual subscription. It can be cheaper for partners. Many open-source products are available in the market, and it would be great if they can be a little bit more competitive in terms of pricing. A lot of startups are looking for an open-source, free, or cheap solution. If they can accommodate such requirements, it will be good for the product in the long run."
"I don't have a problem with the pricing."
"The solution's deployment and licensing costs are very cheap compared to those of its competitors."
"The majority of the components are reasonably priced."
"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
867,676 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
11%
Government
9%
Financial Services Firm
17%
Computer Software Company
12%
Manufacturing Company
9%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business42
Midsize Enterprise26
Large Enterprise69
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise4
Large Enterprise1
 

Questions from the Community

Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
Ask a question
Earn 20 points
 

Also Known As

Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
No data available
 

Overview

 

Sample Customers

Alaska Airlines, Iberia Airlines, Columbia, Skype
Canonical, SAS, Amobee, Play Buzz, Abbott, Aternity, Zerto, Freeman
Find out what your peers are saying about Microsoft Azure DevOps vs. PractiTest and other solutions. Updated: September 2025.
867,676 professionals have used our research since 2012.