Infovista TEMS™ Suite vs. PractiTest

Infovista TEMS™ Suite is very good for different scenarios like : - Cluster acceptance - Network troubleshooting - Performance validation I don`t have yet in mind a scenario which the Infovista TEMS™ Suite is not well suited, but if you have something in mind please feel free to tell me as well.

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

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

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

In comparison with the competition they are better. Faster and more reliable, easy to do analysis with it and it provides lots of easy to use functionalities

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

• Test Reporting
• Defect Management

Incentivized