From 90aecc5e0ea7a429812b533e330741634f2f8a54 Mon Sep 17 00:00:00 2001 From: Alex <131140195+AlexWigren@users.noreply.github.com> Date: Fri, 28 Aug 2026 14:10:43 +0200 Subject: [PATCH 1/2] Create README.md --- .../scientific-paper/week2/README.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 contributions/scientific-paper/week2/README.md diff --git a/contributions/scientific-paper/week2/README.md b/contributions/scientific-paper/week2/README.md new file mode 100644 index 000000000..57b00a75b --- /dev/null +++ b/contributions/scientific-paper/week2/README.md @@ -0,0 +1,30 @@ +# Assignment Proposal + +## Title + +An Empirical Evaluation of Using Large Language Models for Automated Unit Test Generation + +## Names and KTH ID + + - Alexander Wigren (wig@kth.se) + - Dawa Arkhang (arkhang@kth.se) + +## Deadline + +- Week 2 + +## Category + +- Scientific paper + +## Description + +The paper selected was published in IEEE Transactions on Software Engineering + +Unit tests are a key part of ensuring that produced code for software is correct and functional. Manually creating these test have however historically been a very labor intensive task. Recent developments in the field of Large Language Models (LLM) has rapidly expanded its usefulness in various fields of software development, including the automated generation of unit tests. This paper by Schäfer et. al serves as an empirical analysis of the effectiveness of LLM technology for the aforementioned purpose. Concretely, the paper introduces what the authors call "TESTPILOT", an adaptive tool to automatically generate unit tests for JavaScript projects. The authors use several different models in their research and find results that seem to imply that the effectiveness of the approach is influenced by the size and training set of the LLM, rather than just the choice of specific model. + +During our presentation we aim to explore how this technology works, briefly go over found results and compare this approach of unit test generation to other approaches that exist. + +**Relevance** + +Automated generation of unit tests is a key part of DevOps as it helps to save time (developers spend less time creating tests and more time creating deliverable code) and ensure correctness (errors are more likely to be found and corrected before reaching the end user). It is therefore highly relevant to explore this topic further and compare this new approach to other available methods. \ No newline at end of file From 111b9e170f8979937cb4b12a80a408503ce2f6ab Mon Sep 17 00:00:00 2001 From: Alex <131140195+AlexWigren@users.noreply.github.com> Date: Fri, 28 Aug 2026 16:27:39 +0200 Subject: [PATCH 2/2] Fixed folder structure --- contributions/scientific-paper/week2/{ => wig-arkhang}/README.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename contributions/scientific-paper/week2/{ => wig-arkhang}/README.md (100%) diff --git a/contributions/scientific-paper/week2/README.md b/contributions/scientific-paper/week2/wig-arkhang/README.md similarity index 100% rename from contributions/scientific-paper/week2/README.md rename to contributions/scientific-paper/week2/wig-arkhang/README.md