TFS Reviews

We use TFS for source control and we use code to connect to TFS as well. It's all generated and the normal process for a developer; we take the latest coding, and whenever there is a build required, we get the latest from other developers and carry out the build. We also do branching and leveling. I'm a solution architect and our company has a partnership with Microsoft. 

The features such as branching and labelling are very good because they actually help you create a master branch which is a running branch. You can then have other branches like staging correction. I also like the user interface, it's intuitive and easy to use and, most importantly, you can access it from the browser.

When you are trying to connect from Visual Studio code to TFS the integration isn't so easy and I think that could be improved. There's one feature we'd really like to see. If I want to scan through how many files have checked out by name, there are no extensions or plugins available for us to readily get the information from TFS because it's being managed by someone else. As a development partner, we're dependent on them for the details and our preference would be to have the ability to do that ourselves. 

I've used multiple versions of TFS over the past decade. 

The scalability of the solution is good. There are 20 developers in my specific project who use TFS for storing the code repository. We work on multiple projects so there can be anywhere up to 25 people in the company using the product at any one time. It's a development tool so we use it on a daily basis as a centralized code repository.

The initial setup is quite simple. I found information from the Azure DevOps portal and they have a lot of videos. 

This is a good tool for core depository, but there are a lot of thing in TFS you can do: You can automate the entire update process. You can run your sprint and everything, it's a good option enterprise wise. Nowadays everything has DevOps so it's a good thing to use. 

I would rate this solution an eight out of 10. 

The Test Management features.

It has made the management of test artifacts more effective, thus leading to the improvement in the quality of our products from a testing/quality perspective.

For VSTS, more flexibility around the customisation of test reports.

Over two years.

No.

No.

The Microsoft Tech Support team responded very quickly to the requests we made to them.

As a Test Architect, I have used varying solutions. So, it depends on the direction that the company is taking from a tooling perspective.

It was straightforward with help from online help articles and Microsoft documentation.

Microsoft has different licensing models. Each organisation would have to decide which is best for them.

It was client specific. So in this instance, it was the chosen option.

Do a proof of concept to ascertain that it fits with your organisation.

Record and playback is a good feature.

• Tech support needs a lot of improvement
• License is expensive

I've used it for six months.

No issues encountered.

No issues encountered.

No issues encountered.

Their support needs much improvement.

The company chose to switch from HP to Microsoft because of the expense of the licenses.

It was complex.

I don't know the ROI yet.

HP products were also evaluated.

• Source Controlling
• Application Development
• Project Life Cycle

When we applied the CMMI standards in our SDLC we used TFS to force some policies to control the project documentation and source controlling, and to manage the relationship between concerned parties.

TFS administration tools need to be more controlled and easier to use.

I've used it for a total of seven years, and for the last three years, I have used it more as a TFS administrator not only as an end user.

No issues encountered.

No issues encountered.

No issues encountered.

Yes in 2007 we used a different source controlling tool and we faced a lot of issues and with no GUI we had to deal with it using commands which made our life even harder.

TFS, like most Microsoft products, is easy to install use. The initial setup is very easy, all you need to know is the basic configurations that need to be applied.

• Version control
• Code backup

I have spent less time merging code from developers.

They can improve the stability and merging features, especially with SSIS.

I've used this version for four months, and previously I was using TFS2010 for two years.

No issues encountered.

There were some minor issues.

No issues encountered.

I have not needed to contact them.

I have not needed to contact them.

I previously used MS Source Safe and TFS was just the logical progression.

We did it in-house.

You could use a less expensive product, but if you need integration with MS Visual Studio this is the best product.

The system admins evaluated a few products.

As a QA geek, MS Test is the most valuable component.

Being able to easily create new bugs during the execution of a testcase in MS Test, then resume testing is a time-saving feature.

It is very difficult to delete work items from the database. It would be helpful if MS provided a way to simplify that.

I've used it for over three years at three different companies.

No issues encountered.

No issues encountered.

No issues encountered.

I have never needed to contact Microsoft about this product.

I have never needed to contact Microsoft about this product.

I was not responsible for the initial install of TFS, but the setup/config of both requirements, test cases and test plans was straightforward.

We did it in-house.

I was not involved in the buying process.

We use this solution for test management, bug management, and product backlog items grooming.

This solution enables us to link all items usefully, in the way we use Agile.

The most valuable feature is having everything in a single interface, allowing quick and efficient browsing.

The test management interface is not very handy.

I would like to see improved metrics in MTM.

• Change control
• Collaboration
• Change history

TFS has allowed our development team to function better as a group, by keeping code organized, and making it easier to prevent people from stepping on each other's code.

The interface needs work. As it is, it takes a few weeks to get new team members used to using it.

I've used it for two years.

No issues encountered.

No issues encountered.

No issues encountered.

We used GIT, and we switched because TFS was easier to use and maintain.

It was straightforward.

We did it in-house.

We are currently using the free version.

We also lookeed at GIT.