Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Tricentis Tosca
Score 8.8 out of 10
N/A
Tricentis Tosca provides an approach to test
automation that is AI-powered, codeless, and end-to-end so it can test
everything in a complex IT landscape, to ensure business processes
work flawlessly no matter where changes occurs.
Its 160+ technology support helps users test everything at
the UI, API and data layer, including virtually any enterprise, custom,
homegrown and mobile application.
With its model-based approach, Tosca enables business,
QA and IT teams to…
N/A
Pricing
Azure DevOps
Tricentis Tosca
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Tricentis Tosca is better as the first testing tool to introduce in a news organization. I believe it's the testing tool that is the easiest to introduce and adopt. It is oriented toward manual testers that would like to start automation but it is less oriented toward …
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.
For projects having huge set of test cases to be automated can be accommodated by Tricentis Tosca with proper folder structure and best practices implementations. Tosca will be less appropriate for organizations where the number of automation scripts are limited with hardly any scope of increasing the script count or the cost of automation will be more than the cost of having manual resources as Tosca is a licensed tool.
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.
Documentation - struggled multiple times with features not explained very well, or not explained at all
The only support is on Tricentis Forums, where, sometimes, based on 'luck' - you will open a support case, and wait few days until you get the chance to speak with someone from Tricentis and show case your issue
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.
We aim to renew Tosca for our organization. What we lose in license cost is gained by having employee that do not need programming background. We also recoup a lot of the cost on the rapidity of automation. Only the support we might not use as much. I believe Tosca is here to stay at our organization
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.).
It can be a challenge for new users who have never used an automation tool. For example, it is hard to understand the layout of the screen and where to find how to update the data. The interface can be overwhelming at first.
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.
Tricentis team was very supportive. Support is expensive but they helped us at many level. Setting up timeline, implementation, precise questions on automation challenges. We had an account manager and technical people we could as to talk to. Support was generally timely and helping. They often proposed to come on site to help us which would cost more but could be helpful
It would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is betterif the support is betterIt would be better if the support is betterIt would be better if the support is better
okIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is betterIt would be better if the support is better
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.
Tricentis Tosca is codeless and therefore easier to use. It's a great tool for people that would start doing automation and have no coding background. It seems like it has the same capabilities as other test automation suites but I felt it lacked a bit of capabilities on the test management suite such as defects test suites organizations etc
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.
It really had a very good impact on our ROI. We were able to automate most of the apps and layers with in it and get a very short execution time which led to increased releases with in short span of time.
Time to market really improved and efficiency of developing scripts was not too bad.
With built in test dashboards, it was easy to pull metrics and share the insights with management.
