TeamCity :: Code Quality

Code Quality

With TeamCity's numerous code quality features you can be sure your code base is being thoroughly tested from the project's start helping you develop high caliber software.

Duplicates and Inspections viewers enhancements

An improved viewer for browsing the discovered code duplicates and inspections allowing to filter the results by directories.

to the top

Code Coverage, Inspections and Duplicates Search

TeamCity has an unparalleled variation of means for maintaining code quality:

analysis of Java code covered by unit tests
search for duplicated pieces of code for Java and .NET projects
server-side code inspection of Java, JSP, JavaScript, CSS code (more than 600 IntelliJ IDEA's inspections are used)

Coverage

Measure the code coverage for your unit tests with EMMA, an open-source toolkit. TeamCity provides both summaries and detailed reports on code coverage. You can also download the code coverage results and analyze them in IntelliJ IDEA.

Open the screenshot in a new browser window

The coverage statistics is available for projects using Ant and Ipr build runners.

You can now track your projects' classes, blocks, lines and methods covered by the tests using the code coverage statistical graph.

Inspections

TeamCity uses a set of more than 600 IntelliJ IDEA inspections which you can use to analyze:

unused and unreachable code,
declaration redundancies,
performance issues,
dead code.

Check out the results of your code analysis in a browser, and then navigate to a particular string of code in the IDE where you can suppress or resolve the inspection results.

Code inspection is now available for Maven2 projects.

Maven Inspections

With statistical graphs you can now track the number of discovered errors and warnings.

Duplicates

Manually searching for code duplicates in big projects locally can take huge amounts of time, and it is almost impossible to constantly monitor the state of the code base.

TeamCity's solution is automated searching for code duplicates in .Net and Java code just like running a build. Select one of the Duplicates Finder runners and all of the integrated code is constantly checked for duplicates. The search is performed on a Build Agent and detailed reports are available in the web UI, where you can opt to show all or only newly discovered duplicates.

The Duplicates Finder for Java is powered by IntelliJ IDEA and will catch repetitive blocks of Java code in IntelliJ IDEA projects or projects being built by Maven2.

The .NET Duplicates Finder is based on ReSharper's capabilities and will catch similar code fragments of your C# and Visual Basic .NET code in Visual Studio 2003, 2005 and 2008 solutions. TeamCity 3.0 supports C# up to version 2.0 and covers Visual Basic .NET up to version 8.0.

A statistical graph allows you to track the number of duplicates discovered in your code.

Syntax highlighting in Duplicates viewer

The Duplicates Viewer now provides syntax highlighting.

Statistics

With statistical trends you can track the condition of your projects over time. The visual graphs include information about all the builds of a certain build configuration across all its history. You can:

Select time range for each type of statistics
Filter information by data series, for example, by Agent name or by result type
View average values
Filter out failed builds and show only the successful builds
View a build summary information and navigate to the build results page

Build Agents' Workload Statistics

More visual metrics, namely, statistics of Build Agents' activity and their usage during a particular time period are now available.

We are sure you'll find this feature helpful in:

your daily administration activities for lowering your company's network workload
finding and eliminating the gap between the most frequently used computers and those which are often idle
reducing the cost of your hardware resources ownership