Objective 1 has been addressed with the following activities
DSpot: In the second period of STAMP we have focused the research about amplification on the following question: can DSpot amplify test cases that focus on the code changed in one commit and can these test cases detect the behavior change introduced by the commit?
Descartes. The key research question for second period was: can we generate hints that indicate what test improvement actions developers can take to improve their test suite?
We have published a survey about test amplification in JSS, a top software engineering journal. Latest results are under review in EMSE and TSE.
Objective 2 has been addressed with the following activities
- New features in the CAMP tool, including: new strategies to reduce the number of generated configurations to be tested and to select the most relevant configurations; integration with JUnit and JMeter to execute unit or performance tests on the different configuration; runtime monitoring.
- Conduct experiments outside STAMP use cases on two large open-source projects, respectively with 13k and 36k commits, and 2.5k and 48k stars on GitHub, where we detected important issues.
- Publications at IEEE ISSRE, the top conference for software reliability engineering, tutorials and technical talks e.g. at the A-TEST workshop at FSE.
Objective 3 has been addressed with the following activities
- Development of the first crash reproduction benchmark for Java (JCrashPack).
- Extension of EvoSuite for Runtime AMPlification (RAMP) to take the behavior of the software under test into account to generate unit tests (model seeding).
- Dissemination of the results in the scientific community through high-quality publications.
Objective 4 has been addressed with the following activities.
- integrate STAMP tools with Jira Software and Github Issues issue trackers;
- a new Jenkins plugin, a pipeline library and pipelines to enhance CI/CD processes with STAMP features;
- courseware based on documentation, sample pipelines and a Docker image containing a full stack CI/CD environment enhanced with STAMP features, available in DockerHub;
Objective 5 has been addressed with the following activities:
- KPIs have been reviewed and tuned to better match the reality and to provide more interesting results. New metrics have been added to also provide better visualization of results.
- Each Industrial UCs have experimented all the STAMP tools by applying them into their different case projects they selected for evaluation.
- Industrial UCs have incorporated some of the STAMP tools (and technologies) into their CI/CD procedures (e.g. pipelines) and/or their software development processes (either by through project management tools or an IDE).
- Industrial partners have computed KPI metrics, based on conducted experiments, and reported them. From these KPIs measurements, they have drawn conclusions about the effectiveness of the STAMP test amplification techniques on their industrial software development processes.
Objective 6 has been addressed with the following activities
- Collateral. Developed a full range of communication material including an efficient visual identity, 14 videos [18 over 3 years], a tri-fold brochure, an A5 flyer for the beta-testing campaign, a roll-up poster for exhibition, t-shirts for beta-testers.
- Events. Showcased the STAMP projects in 15 industry events worldwide [27 over 3 years]
- Workshops. Three webinars and 16 workshops [20 over 3 years] were organized for in-depth presentations of the tools to academic and industry potential users.
- Communication. The consortium had an on-going communication activity directed at the press and social media.
- Scientific dissemination. The consortium published 12 papers in scientific publications [31 over three years], enabled the completion of three PhD’s papers and participated in dedicated scientific and academic conferences such as ISSRE, ISSTA, ICSE , ICST
