Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions contributions/scientific-paper/week2/wig-arkhang/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Assignment Proposal
Comment thread
algomaster99 marked this conversation as resolved.

## 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.
Loading