Kualitee vs. TestRail vs. Visual Studio Test Professional

From a business standpoint, features such as test scenarios, test cases, bug logging, and then graphical representations of every minute detail related to task and projects are very satisfying and productive. We can keep track of literally everything with Kualitee, and our quality is improving. One downside is that we cannot change the visualisations of some graphs. I believe that by giving the user more customisation options, such as filtering out on the basis of days and months, the experience could be greatly improved.

Incentivized

The integration with other tools, and their user friendly layout and design. It's very comfortable to use and is way better than other tools with the Automation Testing tools, thanks to the great API that is included. Sometimes the integration with Jira is a little faulty, but the links to that tool usually work well. It could be cool if it had a better following for the bug items that were registered on other tools.

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

• Import and Export
• Integration with other tools
• Regression and Blackbox testing

Incentivized

• Managing test plans and test cases
• Generation of test results
• Modularised way of storing tests

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

• Support response time
• Should have dark mode
• Response time for API call

Incentivized

• Outstanding user bugs
• UI is clunky
• Things are not where you think they would be

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

As I am a tester, for me I found this tool to be new in terms of everything like the management of tests, plans, releases, reporting,etc. It is overall a good tool for test reporting and can be used for reference in the future. I liked several features of on the go placement of screenshots. Also I feel like the UI , the font, the color combination can be improved

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

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

TestRail is very costly and complex compared to Kualitee

Incentivized

TestRail definitely saves times. I work in a company that consists of several development teams, all of which have different processes. Some of the teams leverage test cases, some do not. I've noticed that the turn around time it takes for me to pick up a ticket, QA it, and then pass/fail/send feedback is much faster when there is a test case created as I'm not reading through ticket description/comments to figure out what needs to be QA'd.

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.

• If the terminology ( Test Scenarios, modules, components ) is not used in your workflow, it may take some time to set up properly because you must figure out how these are defined by your own terminology to get the hierarchy correct

Incentivized

• We are able to easily pull reports any time management would like to see them
• Jira integration makes it easy to attach to stories/defects and save time
• A quick overview at the system's health as a whole is easy to see from TestRail

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