The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
Currently, I have a project change in my company, and I am working in mainframe technology and mainframe testing. Mainly, I am currently working with Selenium and Java. Regarding Java frameworks, I am working with Cucumber BDD. For Jira, I am currently not using it, but I am using ADO, which is Microsoft Azure DevOps.
Microsoft Azure DevOps provides Agile methodology, and daily we have sprint calls and sprint retrospectives. The stories assigned in the board are in Microsoft Azure DevOps, so every two weeks during sprint planning, the main person managing that board assigns tasks to developers along with the points. The same applies to testers as well, as we need to test the assigned tasks. After two weeks, we either complete that task story or carry it forward. This all will be in Microsoft Azure DevOps, where we periodically check the backlog. The main person will prepare reports, and we raise bugs in Microsoft Azure DevOps. Test planning, uploading test cases, regression test cases, and execution of test cases are all tracked there.
The regression test cases for every story or every month that we have to run are very helpful, as we upload all our regression test cases and execute them along with the evidences. Whenever we go back and refer to the functionality of the earlier one, it is helpful because the test result evidences are also available. The person tracking it finds it very useful, and there is no need to ask for individual reports. If executed there, everything will be in the report when extracted.
I do use Microsoft Azure DevOps Boards for the collaboration part. I am very satisfied with it for collaboration; it is very good. From the beginning till the end we are using it, so it is a good product.
I have not integrated Microsoft Azure DevOps with Micro Focus and currently do not use UFT One, so I think integration with Micro Focus would surely help a lot.
I have been working with Microsoft Azure DevOps for two years.
I would rate stability for Microsoft Azure DevOps as a ten because earlier we had Micro Focus Quality Center, and Microsoft Azure DevOps is a good management tool. I think we can do more with it, especially since today everyone is adopting Agile methodology, covering everything from story planning to sprint planning, retrospectives, and including reports, as well as backlog reports, where many functionalities are available.
I can give scalability an eight.
I had a very good experience with Microsoft technical support. Whenever I raised a ticket or needed help, I received great support. Since I spent most of my career working with UFT One, I can give an eight point five.
When I compare Microsoft Azure DevOps with Micro Focus for my use case, Micro Focus allows me to do only a few things in UFT One or ALM, as some parts were missing, especially in an Agile world. Microsoft Azure DevOps is a more complete product for me.
Microsoft Azure DevOps actually has a simple setup process if we use the cloud version, which requires not much setup. The stand-alone version might take more effort, but the cloud version seems simpler. I do not have much idea except they provide a URL for us, which we just access.
I rate Microsoft Azure DevOps price as a one, which means it is a good value.
In terms of Azure Repos, mainly, I do not take reports myself, but higher management wants reports such as stories backlog reports. They will take these reports. On the testing side, whatever regression percentage is covered, and defects raised and resolved, or assigned and fixed, the authorized persons find it helpful to generate various reports.
Regarding Azure Test Plans, the respective product owner and Scrum Master mostly use all these functionalities. As a tester, I execute whichever story is assigned to me along with the test evidences, even for regression. If a test plan exists, I upload test cases and raise any defects. These are my areas of functionality.
I might have that integration with Microsoft Teams, but since I am currently not using it, it is mainly due to my focus on mainframe testing or Selenium with Java. Others who use UFT or LoadRunner for performance testing might have that integration.
Based on my experience, the main benefits Microsoft Azure DevOps provides include saving time for tracking all assigned stories, as everything from the epic to detailed sessions and links is tracked. Once assigned, developers upload unit test cases that I can refer to. Each and every part and functionality is available, which makes it easy for me to refer to during SIT testing, and for defects raised, we can track to whom they are assigned until closed.
I am satisfied with the functionality of Microsoft Azure DevOps because UFT is for functional testing, but integrating with Microsoft Azure DevOps allows us to track from the beginning to the end. I would rate this product an overall ten.
My primary use case for Digital.ai Release at the bank is to support our production deployments, and I find it an easy tool to use for release and orchestration.
A specific example of how I use Digital.ai Release in a deployment scenario is that we are using it to deploy our applications on production, and one of its strengths is the ability to integrate with other tools, such as Jenkins and Argo CD.
Another aspect of my main use case for Digital.ai Release day-to-day is the ability to use the go or no-go process through the tool with ServiceNow, which allows us to verify the change request and ensure all required approvals are in place, which is important in a bank because our ecosystem is critical.
The best features Digital.ai Release offers in my experience include using it alongside Jenkins, Argo CD, and ServiceNow.
The integration with ServiceNow works well because you cannot deploy some applications on production without a change request in ServiceNow, and Digital.ai Release integrates with ServiceNow to verify all these points for us.
Digital.ai Release has made my work easier and simpler by automating many actions, so I do not have to verify too many points; the tool does it automatically.
Digital.ai Release can be improved by reducing the number of tasks that need to be completed before starting a release, as there are too many tasks to get done.
The interface of Digital.ai Release can be improved as well because on first use, you will feel a bit lost, so we could work on the interface to make it easier to navigate.
I started using Digital.ai Release in my first month, so I have been using it for two years.
In terms of Digital.ai Release's accuracy and reliability of output, I find it all to be good.
Digital.ai Release is deployed in our organization as both public and private, depending on the application.
When I started working at BNP, they had already been using Digital.ai Release, so I do not know how it was before, but it has made our work easier and more simple.
I chose a rating of 8 out of 10 because I tried another tool, and to be honest, I think that tool is easier.
My advice for others looking into using Digital.ai Release is that you need to do some research about the tool to understand what you can do with it and what you cannot do with it, as well as to see some reviews on the internet. I would rate this product an 8 out of 10.
