Provides results on changed code within seconds.

Teamscale knows the commits of all branches in your repository. It can be fully customized which branches Teamscale should analyze.
Trends and other visualizations can be seamlessly inspected on all relevant branches, too.

Limit the allowed length of files and methods using configurable thresholds.

Finds redundant pieces of code that were created via copy&paste. Clone detection is robust against simple modifications, such as rename of variables.

Architecture conformance analysis performs a comparison between your intended specified architecture and the architecture found in the dependencies of your source code.

Checks against configurable rules for names of types, methods, and variables.

Allows to check, whether all of your API methods are commented. Can detect trivial and redundant comments.

Test Gap Analysis reveals untested changes. These are especially error-prone parts in your source code.

Test Impact Analysis selects and prioritizes all relevant regression test cases for individual changesets.

Pareto Testing finds new bugs as quickly as possible by selecting an optimized subset of test cases from your regression test suite.

Ensure that all (safety-critical) requirements to your system are covered and verified sufficiently with Requirements Tracing.

Configure the rules you want to check against, as well as their severity.

Upload and manage metrics and findings from any external source.

Define your own checks using our powerful Java API.

Once uploaded to Teamscale, our tool is able to integrate the results of many external coverage tools.

Teamscale can seamlessly integrate findings produced by third-party tools. Some of these tools will run internally with Teamscale, while the output of other analyzers can be uploaded to Teamscale.

See findings directly in your IDE of choice.

See for each single commit the quality violations that have been added or removed.

Findings tracking follows violations of your quality guidelines across every code change, including file renames of moving of code fragments.

Finding exclusions allows you to hide quality violations that you do not consider relevant. Thanks to tracking, findings remain blacklisted also in case to changes to the surrounding code or when upgrading Teamscale.

Filter quality violations to only display those created after a specific date, such as the start of the current iteration.

Group quality violations and assign them to users. Allow to easily check resolution of these tasks.

Dashboards can be created, edited, and shared by each user to provide customized views on the quality data.

You can create reports in a presentation-like manner, and present them directly out of Teamscale.

Inspect the quality of your system for any historic state.

Search in your source code and commit messages.

Compare snapshots of your system's quality for any two points in time, allowing deeper insight into the changes of your system.