TeamCity Review

Execution of unit tests with code coverage reports is a valuable feature

What is our primary use case?

Automating continuous integration and catching those culprits who introduce build errors or test failures who refuse to test on their own machines.

How has it helped my organization?

Being the sole TDD developer in an organization is not enough if the rest of the team does not test as well. Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end.

What is most valuable?

The three best features are the following:

  • Automated builds triggered on check-in
  • Execution of unit tests with code coverage reports
  • Automated deployment to various environments.

What needs improvement?

Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted. Whether to present an error code or just throw an exception, it was unclear, as well as having to paste a script versus executing a PS file. Fewer "options" in this section with greater consolidation and handling would be appreciated.

For how long have I used the solution?

Three to five years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
1 visitor found this review helpful
1 Comment
Manager, Live Production at a software R&D company with 1,001-5,000 employeesReal User

Thanks for the information!

18 April 18
Sign Up with Email