TFS Reviews

It is easy to push our changes from quality to pre-prod and prod. We also use TFS for maintaining our data.

It is a repository, so all the changes are saved. Also, even if there is some conflict, we have the merge tool and can use it to check the changes made by the developers. We can finalize which one to push to the server.

It would be better if we could bring it out on the cloud.

We have been using this solution for one year, and it is deployed on-premises.

We build a table in TFS and then deploy it using Octopus. It is a slower process, and you can go directly to SSMS and create a table there. However, there is no history if there are any mishaps, so we lose all the changes. So it is better to make those changes in TFS to have a backup. So even though TFS is slower, it is better.

The solution is scalable, and we haven't faced any issues with TFS except for some conflicts we can resolve using the merge tool. We have about 50 to 60 people using TFS. We have about eight people working on our support team.

I rate the technical support a nine out of ten.

The initial setup was straightforward. Deployment time depends on the weight of the package table or solution. It can range from 20 seconds to ten minutes. We completed the deployment in-house.

I rate this solution a nine out of ten.

We use it for code archiving, complete CI/CD functionality, code propagation, code repository, etc.

Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part.

The price could be cheaper.

We're going for a cloud solution that will give us similar functionality and integration with our other products that we are customizing, like SFD. At present, those codes aren't many. 

I've been using it for more than eight years.

It is stable.

It's scalable. We have around 45 users.

We deployed it using an in-house team. You will need two to three people who are in the DevOps teams, who do all the testing, and programmers, who use it and check the code.

You will need to obtain server and account licenses.

TFS is a good product, and I would rate it at eight on a scale from one to ten.

We use TFS for manual testing in our labs and as an automation tool., basically use TFS and we have the shared for that. 

The TFS was previously used for the build repository, but we have moved away from using it and we use other tools for builds. We are moving towards JIRA for other activities, such as cascade management, and test automation management.

The most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful. 

I have been using TFS for approximately seven years.

TFS is highly stable. We have a lot of queries and the test plans can generate for automation purposes and runs very well. I prefer TFS over Jira in this area.

TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools.

We have more than 200 users using this solution.

We use JIRA in parallel with TFS and we are facing a lot of difficulties with JIRA because we do not receive the leverage and the same features in JIRA that we do in TFS. Our preference is TFS over JIRA.

There is some maintenance required from our team. For example, licensing and overall support. 

When the applications are developed in VideoStudio and other technologies. It's preferred to use TFS for all of the management solutions.

I rate TFS a nine out of ten.

We use this solution for test management and defect tracking. 

Most of my work is in the defect area of the solution. I like the attachments which can be directly inserted and highlighted. Users get alerted so they know when there's work required which makes the solution quite efficient. TFS also has filters that help us create a dashboard for monitoring, as well as test and script planning.

I haven't been able to get access to the test case management and execution because it requires an extra license fee. It would be helpful if that was made available to all the users who have already bought TFS.

I've been using this solution for about three years. 

The solution is stable. 

The solution is scalable. 

The features in TFS are similar to those found in Jira. 

The solution came with our Microsoft package so no deployment was required, it was just a matter of clicking on the web link. We currently have more than 500 users and that will increase in the future. 

I rate the solution nine out of 10. 

I use it  for managing. To manage the project in Git and manage branches in projects. 

Merging branches is definitely one of the more challenging aspects for people new to TFS.

I have been using it for three years. 

Stability is okay. I would rate the stability an eight out of ten. 

I would rate the scalability a six out of ten. Sometimes, a lot of branches get mixed together, making it difficult to use. I remember struggling with these branch management issues some time ago and even wrote about them. It is so hard to review problems in TFS.

There are around 200 end users using this solution in our organization. 

I found Git to be a better overall experience. Merging branches in TFS, especially merging to the master branch, could be quite difficult. Git seemed to handle it more smoothly. However, after two years, the company decided to switch to Git.

For experienced users, it might be manageable, but for non-technical users like nurses, branching and merging in Git proved difficult. They often had to ask for help from team members because they found it challenging.

Overall, I would rate the solution an eight out of ten. 

The solution was used for software development.

It is very user-friendly.

Since the TFS was an on-prem solution, the private network accessibility was restricted. 

I have been using TFS for a year. 

It is a stable solution. I rate the stability an eight out of ten. 

It is a scalable solution. Presently, twenty to thirty users are using the solution. 

The technical support team is good and supportive. 

Positive

The IT team deployed the solution. 

There is a yearly licensing fee that needs to be paid. 

I rate the overall solution a nine out of ten.

I use TFS to assign and manage projects.

TFS's best features include user-friendly test management, bug reporting, and ID assignment.

TFS's CI/CD, project pipelines, and management development could be improved. TFS is also an older product, so it's not making the advances that other products in the market are.

I've been using TFS for seven years.

TFS is very stable.

TFS is a very scalable product.

I would rate TFS eight out of ten.

I use this solution in my organization as a product owner who manages backlogs in DevOps. I manage the backlogs items and use it to collaborate with my developers.

There are less than 100 people using this solution in my company.

The solution is deployed on-cloud.

It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration.

I only use 1% of the functionality, so I am not familiar enough to know what needs to be improved.

I have been using this solution for a couple of years.

It's stable.

It's scalable.

I would rate this solution five out of ten.