Azure DevOps Services Formerly VSTS vs TestComplete

[Azure DevOps Services (formerly VSTS)] is well suited for agile teams. It is a digital kanban for teams to access anywhere at any time. Especially during covid when most companies are still remote, it allows teams to fully perform and still be functional in operating within an agile methodology. It also gives visibility to teams capacity.

To really make the most of TestComplete, at least some scripting is necessary. TestComplete works really well with clearly identifiable objects but needs some tweaking for objects that vary in e.g. quantity. We have some elements that vary, but the vast majority of UI elements have unique identifies, and those iterative elements can also be mapped to iterations of a semi-unique element (so more of a mapping of the item type that the specific item). I doubt the usability would be near as good if more items were not clearly identifiable. In our case, most are, and we handle our tests in form of nested keyword tests that occasionally also implement scripting when needed. Tedious tests like Verification of the correct presence and status of UI elements in all possible scenarios, and iterative tests of e.g. input values and combinations of such, are made easy to set up, execute and evaluate.

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

• TestComplete is great for working with our non-web applications.
• TestComplete allows us to interface with our web application in a robust way.
• Despite the age of our architecture, TestComplete handles the old stuff that's been around a while as well as the newer technology when we are able to implement it.

• Column sorting when in filtered states.
• A way to show cross-team dependencies.
• A customized "From" field for notifications. Sometimes when a mail comes from Azure DevOps the teams do not realize that I am sending it
• A way to do online poker that doesn't require a plug-in.

• Would love to see TC be a plugin for Visual Studio. Instead of VBScript or JavaScript, to use C# or VB.NET
• Easier to set up with iOS. Android is not bad but iOS seems slow and confusing to get up and running
• Built-in PDF reading support, built in Excel API

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.

We have bigger test automation pack using test complete at the same time we also think this is not good performing tool for large number of test automation scripts.

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.

It is usable when you become accustomed to its quirks. Not using it for two months and then you need to re-learn the quirks for some features (but some quirks are so awful that they will never fade from your memory). So, when using it regularly, it is possible to be quite productive, if no big correction in name mapping is needed.

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.

Some bugs were quickly resolved, but most UX quirks of the tool are just marked "as designed". No follow up for enhancement request.

Was not part of the process.

If you develop a mobile application and your testing process goes in cloud, probably you will face a problem - how to implement a stable connection between your mobile devices and testing servers

Azure DevOps is much easier to implement and use on a daily basis than VersionOne. This is based on end-user feedback and my personal experience as well. ADO has more features and seems to get updated more frequently than VersionOne as well. VersionOne is less expensive overall than ADO, but our company prefers to use ADO because it has a lot more benefits.

TestComplete stacks up against them in terms of GUI and seamless performance. It records each and every step and action been performed in the application and produces a detailed report in a well-structured manner. It can connect and access seamlessly among various databases directly to speed up the testing process.

• It provides a great IDE to make things easier, clear, and compact. It has always been a positive ROI
• It's worth the money. I don't think any other software could replace the VS. It has helped us a lot to making things ready on time
• The only thing I dislike is that it takes a lot of memory space when in an idle state

• On one of the applications, I've reduced the testing time from a month to five days.
• I don't always have time to create tests for new features, then I revert to manual testing.
• The Zephyr reports have given management insight on what happens in the QA department.