Azure Test Plans vs. PractiTest

It works well for express test case implementation with a short duration. You can define the tests for two weeks and run the activities documenting the software errors and fixes to control the effectiveness of DevOps. The graphic reports give the idea of the backlog phases advances and errors detected. It needs improvement if you have a large test project and need to design financial budgets and control over costs of the test plan.

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

• Integration with Azure Boards
• Integration with Visual Studio 2022
• Automation using Pipelines and releases
• Real time dashboards
• Integration with code repositories

Incentivized

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

Incentivized

• Graphic definition of the the Work Break Down Structure
• Gantt Chart to check the activity dependance and flow of the process
• Basic cost module to design test budgets.

Incentivized

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

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

Test rail feels quite dated compared to Azure Test plans and Devops as a whole. Functionality and ease of use is actually night and day.

The ability to create structured test plans with ease that can be traced and attached to Epics and stories with relevant tasks allows the system to feel superior in everyway compared to Test rail which had a slow web interface

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

• Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting.
• The most valuable features of Microsoft Azure DevOps are high-level protection. Protection is very important to the customers to prevent eavesdropping.

Incentivized

• Test Reporting
• Defect Management

Incentivized