We performed a comparison between Microsoft Azure DevOps and PractiTest based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment."
"It's a great product for the CI/CD process."
"Fields can be customized and the reporting is good."
"Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
"DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this."
"Our technical sales staff and business development people need to know how far the developers are on any product that we're developing. DevOps makes it easier for you to see how far along they are with the work because they have a repository where they store everything. There is a portal where you can see what has been done, what has been tested, what is working, and what isn't. I have a huge dashboard with an overview of what the development team is doing from an executive point of view."
"Overall, so far we have no major issues to report."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"The solution could be made faster because it can be a little unnerving to browse through too many pages and press too many buttons."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"I would like to see improvement in the metrics and the dependencies."
"Microsoft Azure DevOps could improve by having better integration with other email servers."
"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."
"Another area is the Azure monitoring agent for Citrix machines. There's room for improvement there too."
"We are currently in the process of moving all of our on-prem to the cloud platform. We are trying to make that move and host the majority of our DevOps services in the cloud because the cloud is where most of the things are going nowadays. However, the process of this transfer is not straightforward, and it could be a lot easier. Microsoft hasn't provided the maturity for migration tools. It could be a lot easier in that respect. I want to see them continue to advance the API capabilities. They could add some more robust functionality to the administrative layer within ADO services. There are a lot of configuration elements that you need to take care of at the organization level and the project configuration level from an administrative capacity. When you're dealing with process templates and things of that nature, you have to do them all manually. Being able to automate some of that using scripts or API functionality would be really nice."
"It doesn't allow you to connect to multiple different tracking tools."
Earn 20 points
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 127 reviews while PractiTest is ranked 20th in Application Lifecycle Management (ALM) Suites. Microsoft Azure DevOps is rated 8.2, while PractiTest is rated 8.8. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". On the other hand, the top reviewer of PractiTest writes "Offers one click graphical dashboard reports and advanced customization". Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management, whereas PractiTest is most compared with TestRail, Jira and Zephyr Enterprise. See our Microsoft Azure DevOps vs. PractiTest report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
