Azure DevOps Server (formerly TMS) vs Micro Focus UFT One

• The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
• Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
• Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.

Read full review

• The simple front end will allow novice users to easily grasp the basics of automation and give them confidence to try things for themselves.
• UFT can scale up and run across multiple machines from a single controller, such as ALM, enabling hundreds of tests to be executed overnight.
• There is an active support community out there, both official HPE based and independent users. This means if you do encounter a problem there is always someone out there to help you.
• The later versions have many add-ins to plug in to other tools within the QA world.
• Expert users are able to utilise the many native functions and also build their own to get the most out of the tool and impress people as they walk past and see the magic happening on the screen.
• UFT also has LeanFT bundled with it, allowing automated testing at the api level - if you can convince the developers to let you in there.

Read full review

• The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
• VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
• Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.

Read full review

• The biggest disadvantage is that the cost is very high for licensing and maintenance.
• We cannot run multiple threads/instances like in case of Selenium Grid.
• Since it supports only VB script, the Object Oriented approach to test automation is challenging.
• Need to buy different add-ins- Java, Oracle, SAP, .NET, etc.

Read full review

• Time to completion for projects has significantly gone down by 15% and that number changes as more people are trained and are comfortable with TFS.
• Change Management and Approvals are easier to access.
• More projects are implementing SCRUM methodologies for applications

Read full review

• Reduces the total workload of keeping the team to test older (regression) functionality. QA testers can concentrate on ad-hoc and exploratory testing, saving time and effort across the entire project.
• Has built a better infrastructure for the client applications on which we can rely on for stability and providing regression results for any new features being developed.
• Led the applications a step closer to implementing agile practices and DevOps across the entire organization. Thus, providing a better turnaround time of new features to the customers and less maintenance headaches for the BAU team to address.

Read full review