Coverage Profiler Overview
This page contains sections that illustrate how to set up coverage profiling for various languages and environments. Each language has a set of profilers that can be used in order to record coverage. The following contains a list of coverage tools that we recommend you use to obtain code coverage for your tests. These are tools that we have used successfully together with our customers in the past. However, other tools may work as well.
Third-Party Tools
Please note that we are not the vendor of most of these tools and thus cannot directly support you in case you face problems with their setup. Please contact the appropriate vendor.
We will gladly help you to set up the upload of their coverage report files to Teamscale and to use our Test Gap Analysis.
If you work with a coding agent, it can set up the coverage recording and upload for you:
Set up coverage recording and Test Gap analysis. Use the Teamscale documentation at https://docs.teamscale.com/llms-full.txt Follow the best practices from https://docs.teamscale.com/introduction/best-practices/external-coverage-uploads/ Ask me for the URL of my Teamscale instance, my project ID and my username and access key. If the repository contains a .teamscale.toml file, take the URL and project ID from it. The instance serves its REST API spec at <url>/openapi.json (public, versioned) and <url>/openapi.json?include-internal=true (also internal endpoints, which may change between releases). Ask me before modifying settings or performing destructive operations. Let me enter any credentials you need in a secure way so they don't leak to the agent transcript.
⚠️ Never paste your access key or other credentials into an agent session! It would leak into your session transcripts.
Paste this prompt into your coding agent, for example Claude Code or GitHub Copilot.
