STAMP · Project

Automated Software Testing Tools That Let You Ship Code Updates Faster and Safer

digitalTestedTRL 6

Imagine you run a software company and every time your developers push a code update, someone has to manually check that nothing broke. Companies like Netflix push hundreds of updates a day — they can do that because they have incredible automated testing. STAMP built open-source tools that take your existing tests and automatically multiply them, generating new test cases for every code change. Think of it like a spell-checker that not only catches typos but also writes new proofreading rules every time you edit a document.

By the numbers

consortium partners across 8 countries

industry partners including 5 SMEs

50%

industry participation ratio in consortium

EUR 4,307,070

total EU research investment

working demo tool prototypes delivered

TRL 6

target technology readiness level

total project deliverables produced

The business problem

What needed solving

European software companies lose competitive ground because they ship updates slowly, held back by fear that insufficient testing will push bugs into production. Manual testing is expensive and cannot keep pace with continuous delivery — where leaders deploy hundreds of code updates per day. The result is longer release cycles, higher costs, and missed market windows.

The solution

What was built

The project delivered 8 working tool prototypes including a unit test amplification tool, a configuration amplification tool, online test amplification services, and a crash replication benchmark. All tools were built as open-source microservices targeting TRL 6, designed to plug into existing DevOps pipelines.

Audience

Who needs this

Software companies practicing DevOps or continuous deliveryeHealth platform providers shipping regulated software updatesSmart city solution vendors managing complex multi-service deploymentsContent management system developers maintaining large codebasesPublic administration IT departments modernizing legacy systems

Business applications

Who can put this to work

Healthcare IT / eHealth

mid-size

Target: eHealth platform providers and health-tech companies

If you are an eHealth software company dealing with the pressure of frequent updates to patient-facing applications while needing to meet strict regulatory testing requirements — this project developed open-source test amplification tools that automatically generate new test cases from your existing tests every time code changes. With 5 software companies involved in development across 8 countries, the tools were built for real-world DevOps pipelines.

Smart City Technology

any

Target: Smart city solution providers and IoT platform companies

If you are a smart city technology vendor struggling to test complex, multi-service deployments before each release — this project built configuration amplification tools that automatically test different deployment setups and catch compatibility issues. The tools are open-source microservices designed to integrate into your existing CI/CD pipeline, targeting TRL 6 readiness.

Enterprise Software / SaaS

enterprise

Target: Content management and enterprise SaaS companies

If you are an enterprise software company where manual testing bottlenecks slow down your release cycle — this project created unit test amplification tools that reuse your existing test cases to automatically generate broader test coverage. The consortium of 16 partners including 5 SMEs validated these tools against real industry codebases in eHealth, content management, and public administration.

Frequently asked

Quick answers

What would it cost to adopt these testing tools?

All STAMP tools were developed as open-source software and built as microservices for easy integration. There are no licensing fees for the tools themselves. Costs would come from integration effort into your existing DevOps pipeline and any customization needed for your specific technology stack.

Can these tools handle large-scale enterprise codebases?

The tools were designed and validated with 5 software companies operating in eHealth, content management, smart cities, and public administration. The project targeted TRL 6, meaning the tools were demonstrated in relevant environments. However, scaling to very large codebases may require additional configuration and performance tuning.

Who owns the intellectual property and how is it licensed?

All solutions were explicitly developed as open-source software. This means your company can adopt, modify, and deploy the tools without IP restrictions. The open-source approach was a deliberate project design choice to maximize adoption across European industry.

How do these tools integrate with our existing development pipeline?

STAMP tools were built as microservices specifically to facilitate integration with existing DevOps workflows. They act at three levels: unit testing, configuration testing, and production monitoring. This modular design means you can adopt one component at a time without overhauling your pipeline.

Is the project still active and are the tools maintained?

The project ran from December 2016 to November 2019 and is now closed. The open-source tools remain available, but active maintenance depends on the community and the original consortium partners. Based on available project data, check the project website for current repository status and community activity.

What evidence is there that these tools actually work?

The project produced 8 demo deliverables including enhanced prototypes with performance reports for both the unit test amplification tool and the configuration amplification tool. A crash replication benchmark was also delivered, providing measurable validation. The consortium included 8 industry partners who tested the tools against real software systems.

Consortium

Who built it

The STAMP consortium is notably industry-heavy with 8 out of 16 partners from industry (50%), including 5 SMEs — a strong signal that the tools were built for real-world use, not just academic papers. The 3 academic partners brought software testing research expertise, while 5 software companies from eHealth, content management, smart cities, and public administration served as validation environments. Spread across 8 countries (ES, FR, IT, NL, NO, RO, SE, TR) with coordination from Sweden's KTH Royal Institute of Technology, the consortium had broad European coverage. The EUR 4,307,070 investment and 27 deliverables suggest substantial engineering effort behind the 8 demo tools produced.

KUNGLIGA TEKNISKA HOEGSKOLANCoordinator · SE
INSTITUT NATIONAL DE RECHERCHE EN INFORMATIQUE ET AUTOMATIQUEparticipant · FR
STIFTELSEN SINTEFparticipant · NO
OW2participant · FR
ACTIVEEONparticipant · FR
SINTEF ASparticipant · NO
ATOS SPAIN SAparticipant · ES
TELLU ASparticipant · NO
UNIVERSITE DE LILLEthirdparty · FR
ENGINEERING - INGEGNERIA INFORMATICA SPAparticipant · IT
ATOS IT SOLUTIONS AND SERVICES IBERIA SLthirdparty · ES
UNIVERSITE DE RENNES Ithirdparty · FR
TECHNISCHE UNIVERSITEIT DELFTparticipant · NL
XWIKIparticipant · FR

How to reach the team

The project was coordinated by KTH Royal Institute of Technology in Sweden. SciTransfer can help identify the right contact person.

Order a report on this consortium See KUNGLIGA TEKNISKA HOEGSKOLAN profile →

Next steps

Talk to the team behind this work.

Want to know if STAMP's automated testing tools fit your DevOps pipeline? SciTransfer can assess compatibility with your tech stack and connect you with the right consortium partner.

Order a report on this topic More in Digital & ICT