Azure DevOps Server vs. PractiTest

In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate

Incentivized

For most of the test case scenarios, PractiTest works fine. If we talk about one specific feature then it would be the automation side. I like this feature a lot just because it made all testing so easy and effortless but on the other hand automation in this platform comes with so many limitations and that's where I am not fully satisfied.

Incentivized

• Vast range of Template for Automated Build and Release Pipeline with option to have conditional triggers
• Code repository mechanism is aligned with GIT which is a well known public repository system
• Bug Management is also an integral feature of this tool
• Dashboard creation option of Build and Release pipeline is also available

Incentivized

• Effective Test case template.
• Can integrate with different Atlassian products.
• Report generation.

Incentivized

• Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
• Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
• Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.

Incentivized

• Better dashboard display capability (drag and drop to rearrange gadgets)
• Creation of global user groups (as opposed to just project groups)

Incentivized

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.

Incentivized

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.

Incentivized

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

Incentivized

The chat button is available to anyone who logs into PractiTest. In my experience, the support has always been very quick, very friendly, and very thorough. They make sure that your question is answered in a way that you understand it. They also provide documentation of best practices so you are never left hanging on what to do next.

Incentivized

Do research beforehand and, if possible, do a trial run before implementing into production environment.

Incentivized

Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.

Incentivized

I've used many different Test Case Repository tools, and while each of them has its perks, I like the capabilities of PractiTest best. When creating a test in qTest for example, you can only input information into the fields provided, and you have everything set up in a folder tree structure. With PractiTest, we are able to create custom fields and filter our tests based on those fields to provide more accurate information in a readily available format while quickly searching for the filter instead of through a folder tree. TestRail did not appear to meet our needs as a company. It just didn't have the potential that we found with PractiTest. Zephyr for example worked seamlessly with Jira, which is really nice since that is what we use for the most part. However since we cater to many different clients, we needed an external Test Case repository so we could use something that wasn't tied to 1 Jira instance.

Incentivized

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

Incentivized

• Test Reporting
• Defect Management

Incentivized