Draft:Teamscale
Submission declined on 17 July 2026 by DoubleGrazing (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
Submission declined on 17 July 2026 by EaglesFan37 (talk). This draft appears to contain text generated by a large language model (such as ChatGPT). You cannot use LLMs to generate article content.
Declined by EaglesFan37 10 days ago.LLM-generated pages with certain obvious signs of being machine generated may be deleted without notice. These tools are prone to specific issues that violate our policies:
Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject. See the advice page on large language models for more information. | |
Comment: Most of the papers cited are (co-)authored by representatives of CQSE, and therefore clearly not independent. I also suspect that Imbus AG, whose staff authored source #3, have some relationship with CQSE. The last two papers look like they might be independent, but don't seem to provide significant coverage of Teamscale. Source #5 looks (on the surface, at least) the best of the lot, but it alone isn't enough to satisfy WP:GNG. We need to see significant coverage, directly of this product and not some related topics, in multiple secondary sources that are reliable and entirely independent of the subject. DoubleGrazing (talk) 08:53, 17 July 2026 (UTC)
| Teamscale | |
|---|---|
 | |
| Developer | CQSE GmbH |
| Release | January 13th, 2014[1] |
| Operating system | Cross-platform |
| Type | Static and Dynamic program analysis |
| License | Proprietary |
| Website | Official website |
Teamscale is a proprietary software intelligence tool made by CQSE GmbH that runs static and dynamic quality analyses[2] for code, tests, issue tracker work items, architecture models, Simulink models and requirements.[3] It is available as software as a service and can be installed on-premise.[3] It received positive media coverage and was used in multiple software quality research studies.
History
[edit]Teamscale is the commercial successor to ConQAT (Continuous Quality Analysis Toolkit), an open-source software quality toolkit created at the Technische Universität München.[4] The first version of Teamscale was released on 13th January 2014 as a purely static code analysis tool. The first dynamic analysis, called Test Gap analysis, was added in version 2.0 in 2016.[1]
Reception and Impact
[edit]Teamscale was reviewed extensively in an article in the German iX magazine. The article found both positive and negative points, like a “large range of functions” and “fast feedback during iterative development and frequent changes”, but also that “initially, there is a high barrier to entry until all systems are correctly connected.”[3]
Teamscale has been the subject of several scientific studies. A paper published in the Empirical Software Engineering Journal in 2026 analyzed the static code analysis findings of Teamscale and how helpful they are in practice to developers.[5] A paper published on the IEEE International Conference on Software Maintenance & Evolution (ICSME) analyzed the long-term impact of using the tool in 41 software systems at Munich Re.[6] Another paper published in IEEE Software in 2025 analyzed how the tools reported test gaps could be prioritized with quality data from 8 different software systems systems at both Munich Re and LV 1871.[7]
The tool's source code was also used in a study from 2024 to augment the Technical Debt Dataset, a research dataset on technical debt,[8] and in 2026 to study method name generation.[9]
CQSE GmbH was nominated for the Deutscher Gründerpreis 2018 (German Entrepreneur Award) for their work on Teamscale.[10]
Incremental Analysis
[edit]
Teamscale's distinguishing feature is its incremental analysis engine.[3] This contrasts with batch analysis, which most static program analysis tools employ. In batch analysis, the entire source code of a software system is re-scanned after each change. In incremental analysis, information about the previous code state is retained between runs of the tool so that only the changed portions have to be re-scanned, leading to faster feedback on newly introduced quality issues.[3][4] This allows the tool to scan every single commit.
Dynamic Analyses
[edit]
Teamscale started as a static code analysis tool, but later on several dynamic analyses were added. This holistic approach to software quality distingishes it from many other tools in that area.
Most notably, it determines the test coverage of not only automated but also manual tests and correlates that with recent code changes to find so-called test gaps: methods that have been changed but not tested. This data is visualized using treemaps.[3]
Coverage data split by test case is furthermore used for a test impact analysis.[3]
A so-called defect analysis uses data about historic bug fixes from issue trackers and dynamic quality data like test coverage to facilitate a root-cause analysis of these bugs.[11]
A usage analysis shows how often each part of the source code was used in production environments.[2]
References
[edit]- ^ a b "A little history of Teamscale". teamscale.com. Retrieved 2026-07-15.
- ^ a b Haas, Roman; Niedermayr, Rainer; Juergens, Elmar (2019-05-26). "Teamscale: Tackle Technical Debt and Control the Quality of Your Software". 2019 IEEE/ACM International Conference on Technical Debt (TechDebt): 55–56. doi:10.1109/TechDebt.2019.00016.
- ^ a b c d e f g Weise, Carsten; Singer, Christoph (2023). "Softwarequalität mit Teamscale steuern". iX – Magazin für professionelle IT (in German). No. 4. Heise Medien. pp. 64–67.
- ^ a b Heinemann, Lars; Hummel, Benjamin; Steidl, Daniela (2014-05-31). "Teamscale: software quality control in real-time". Companion Proceedings of the 36th International Conference on Software Engineering. ICSE Companion 2014. New York, NY, USA: Association for Computing Machinery: 592–595. doi:10.1145/2591062.2591068. ISBN 978-1-4503-2768-8.
- ^ Ye, Liwei; Nie, Yuge; Zhou, Yufei; Yang, Yibiao; Lu, Hongmin; Qian, Junyan; Zhou, Yuming (2026-06-12). "Line-level bug-finding power of static analysis rules: a case study of Teamscale". Empirical Software Engineering. 31 (164). doi:10.1007/s10664-026-10895-3.
- ^ Steidl, Daniela; Deissenboeck, Florian; Poehlmann, Martin; Heinke, Robert; Uhink-Mergenthaler, Bärbel (2014-09-29). "Continuous Software Quality Control in Practice". 2014 IEEE International Conference on Software Maintenance and Evolution: 561–564. doi:10.1109/ICSME.2014.95.
- ^ Haas, Roman; Sailer, Michael; Joblin, Mitchell; Juergens, Elmar; Apel, Sven (2025-03-28). "Prioritizing Test Gaps by Risk in Industrial Practice: An Automated Approach and Multimethod Study". IEEE Transactions on Software Engineering. 51 (5): 1554–1568. doi:10.1109/TSE.2025.3556248. ISSN 1939-3520.
- ^ Graf-Vlachy, Lorenz; Wagner, Stefan (2024-04-14). "Different Debt: An Addition to the Technical Debt Dataset and a Demonstration Using Developer Personality". Proceedings of the 7th ACM/IEEE International Conference on Technical Debt: 31–35. doi:10.1145/3644384.3644475.
- ^ Fein, Benedikt; Jungwirth, Maximilian; Fraser, Gordon; Kandlinger, Florian (2026-02-17). "Challenges of deploying code embeddings: an industrial case study on method name generation". Automated Software Engineering. 33 (2). doi:10.1007/s10515-026-00592-2. ISSN 0928-8910.
- ^ "CQSE GmbH | Deutscher Gründerpreis". www.deutscher-gruenderpreis.de (in German). Retrieved 2026-07-15.
- ^ "Defect Analysis | Use Defect Analysis to Find Bug Hotspots | Teamscale". teamscale.com. Retrieved 2026-07-15.
- provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements;
- are reliable: from reputable outlets with editorial oversight;
- are independent: not connected to the subject, such as interviews, press releases, the subject's own website, or sponsored content.
Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia.