Azure DevOps vs. Tuskr

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

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.

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

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

• I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
• The wiki is not the prettiest thing to look at, so it could have refinements there.
• It could improve the search slightly better.

• 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

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Tuskr suits our organization needs

Incentivized

It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).

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

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

Was not part of the process.

Incentivized

Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.

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.

• We have saved a ton of time not calculating metrics by hand.
• We no longer spend time writing out cards during planning, it goes straight to the board.
• We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.

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