Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
BMC AMI DevX
Score 9.3 out of 10
N/A
BMC AMI DevX is an integrated software platform that provides mainframe development teams with modern Application Development and DevOps capabilities. The solution connects traditional mainframe environments with contemporary development practices through components for source code management, testing, debugging, and analytics.
N/A
Visual Studio Test Professional
Score 7.0 out of 10
N/A
An add-on for the Visual Studio IDE, Visual Studio Test Professional subscription helps teams drive quality and speed. It includes test case management and collaboration features that streamline quality control and support continuous delivery.
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
Our dev team is used to developing with Microsoft tools and managing projects with Azure devops server and service. QA uses the same collaborative platform, so it was easier - almost natural - for all of them to use Visual Studio Test Professional, with full integration and …
Visual Studio Test Professional is head and shoulders above the other options we've tested and used in the past. Our Legacy teams were still using Quality Center as of a month ago and they just switched over to Microsoft Test Professional to join the rest of the organization …
Test Professional is a much more rounded product by nature of its integration with Team Foundation Server. Much lower administrative effort required as only one system needs to be hosted.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.
It would be well suited if we used it with Azure DevOps as we can effortlessly integrate the test cases and even stories or tasks to stay on track with our work. Those test cases can even be reused across multiple projects. Using any other third-party tools, such as Jira, can be less appropriate, as it's not a Microsoft tool, and its capabilities will be limited.
The tool I use is fairly intuitive. It doesn't take long to be using it full time.
Changing the layout/view is fairly easy. This allows it to fit individual preferences.
It is helpful to be able to view specific windows in full screen. Usually, I have it set up to view multiple windows, but sometimes, I just want to view one window in full-screen mode.
The user community of the Visual Studio Test product is weak. For instant problems with this product, it is necessary to quickly reach the source of the error.
Licence fees need to be more reasonable. License prices need to be reduced so that they can easily compete with free testing tools.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
It is very usable if you are familiar with Visual Studio to begin with. If you are new to the interface, it can be a long ramp up period for Testers not used to the GUI. There is always the web option which seems to be more intuitive for many Testers.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.
Visual Studio Test Professional is backed up by the full support of the Microsoft Corporation. That means twenty-four/seven customer support by quality, highly-trained professionals who understand every possible issue that you have experienced before. They are nice, efficient, and highly professional. I recommend them.
The installation teams for these products have never complained about any difficulties during the integration of this range of tools into our IT system.
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
Possitive impact. It is main product suite to enable devops in the mainframe applications team. All developers use these on day-to-day work.
Negative impact: Recent usability issues caused disappointment in the application teams. It became hard motivate the development community to increase usage.
One of the positive ROIs of Visual Studios is the fact that it makes producing our work at a quick rate, things like Intellisense make our work get produced at a much higher rate which is good for our return of investment.
Testing by the developers has increased by 23%, we now take the time to actually test our product before we send it to our QA people.
I am not aware of any negative ROI aspects to our company that have been found.
