PractiTest vs. Tuskr

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

Tuskr works well for teams that want a straightforward test management solution without a steep learning curve. It's especially useful for Agile projects where frequent testing and collaboration are important. Teams looking for extensive enterprise-level customization or highly advanced reporting may find some limitations, but for day-to-day QA management, it performs very well.

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

Incentivized

• Its easy to import test cases in Tuskr by using the csv import feature
• Test runs are easy to create and can include test cases from multiple suits.
• Reports of test runs make it easier to track all the cases that were covered at a particular instance before giving a release signoff.

Incentivized

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

Incentivized

• When you click into a specific test, the status automatically clears. it would be nice for this to be preserved when clicking in instead of clearing
• It would be nice to be able to add comments specific to certain steps in each test, instead of just one big comment box
• Since we use Tuskr for QA, we structure it as a table with instructions and expected results. because these are side by side, sometimes it is hard to go in a step-by-step order when there are multiple QA steps to take to complete the test.

Incentivized

Tuskr suits our organization needs

Incentivized

The Tuskr App, overall rating depends on its easeiest way to use as their features and managment tool are too good. If you need a easier tool and cost-effective tool and a lot of feature in it. and its return of investment is very good. And the software is really ease to adapt

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

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

I have not worked with related testing suite before but Tuskr has been the favorite platform for running test suites. It has generated positive leads from the company data by offering the necessary testing support. It is easy to integrate with other applications to suit business demands. The system generate results from various testing suites that can shared with our clients.

• Test Reporting
• Defect Management

Incentivized

• Everyone in the team can go and read how to perform a specific test and note down the result of it which can be viewed by anyone
• We can filter based on results understanding what test cases are failing from previous runs
• Helps save a lot of time, effort and minimises future issues

Incentivized