FogBugz vs. Tuskr

FogBugz has been a very useful tool to our organization, and much preferred over other options we reviewed, mainly JIRA. There are still some improvements needed, but with the fairly recent acquisition by DevFactory, we have a great deal of hope for what is in store given DevFactory's focus and transparency. It seems like both DevFactory and FogBugz customers are eager for substantial improvements on the front-end, but there is/was a great deal of backend housecleaning that definitely needed to take place first.

Incentivized

Its interface, features and dashboard which help a lot to streamline the workflow. And its really very ease to use. My team and I just use this software and adapt in a week. I surely recommend to any organisation, in regards of pricing, features and interface. And their customer support.

• Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA
• The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.
• Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.

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

• The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.
• There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.
• There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.

• 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 test case management and automating repetitive tasks, Tuskr saves significant time for my QA teams. The whole process was very easy for my team to adapt and get comfortable with other software. We were continuously able to improve our business and this had a significant positive impact on customer satisfaction and retention.

Incentivized

I like JIRA a lot better than Fogbugz for many reasons. If I had a choice, I'd use JIRA every time

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.

• Saves time by quickly allowing Developers to make the necessary notes without getting bogged down in bloated UIs
• Has allowed us to look back easily and see the exact code changes made for the exact Case to aid in decisions for current changes, increasing the certainty of the decided path, without regression

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