National Instruments TestStand vs. PractiTest vs. Visual Studio Test Professional

PractiTest works GREAT as a test case repository. It is very easy to gather metrics, filter, and sort based on custom fields. We were able to work with the API to pull our automation results in as well. The support team is always very quick with their responses and monitors the "in-app chat." They are very open to answering questions, providing best practice materials, and looking for additional feedback. If you already have a central location for all of your test cases and testing needs, then I guess you probably wouldn't need to add another. However, PractiTest has high capability and potential, so if it's set up properly you can easily save time managing your tests.

Incentivized

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.

Incentivized

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

Incentivized

• Availability of the desktop client or the web interface. The web interface being the favorite and providing a better experience.
• It enables you to write unit tests with so much ease.
• Allows the recording and repeating of manual tests
• It can be set up for collaboration.

Incentivized

• Linking the defect with Jira throws an error quite some times which can be improved in the future.

Incentivized

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

Incentivized

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.

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

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.

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

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.

• Test Reporting
• Defect Management

Incentivized

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

Incentivized