2.9 KiB
2.9 KiB
type:: REVIEWS tags:: year:: 2025 venue:: MODELS-WS full-title:: Generation of Unit Tests for Test-Driven Development using Large Language Models date-start:: 30-07-2025 - 12:22 date-submitted:: external-links:: status:: DONE deadline-submission:: file:: @Generation of Unit Tests for Test-Driven Development using Large Language Models parent:: todoist:: https://app.todoist.com/app/task/15-nathanael-yao-juergen-dingel-and-ali-tizghadam-generation-of-unit-tests-for-t-6cVfQ9gQhx4Hq826 collapsed:: true
- ### [[Highlights]]
- ### [[Comments]]
- **SUMMARY** The paper presents an approach based on generative AI, to support Test-Driven Development (TDD) by automatically generating unit tests from high-level user-defined goals. The approach is supported by a prototype developed primarily for the network domain and evaluated through manual checks and feedback from an industrial partner.
- **COMMENTS ** The work addresses an important topic, and the idea of generating tests from user-specified goals rather than implementation code is interesting. However, I have some concerns about the presentation of the work as detailed below:
- The presentation of the proposed approach, especially in Section 5, is not effective. The steps involved in refining high-level goals into subgoals and generating unit tests are described in a confusing manner, with unclear distinctions between what is generic and what is application-specific.
- The human involvement in the process, how feedback is integrated, and how the iterative nature of TDD is supported remain ambiguous. Figures, particularly the algorithm in Figure 1, do not enhance understanding; a more concise representation of the three main steps of the process would be more appropriate.
- The explanation of the pool of basic actions raises some questions: Who defines these actions, whether they are domain-specific, and how they scale to arbitrary user goals, as claimed, is not clarified. Similarly, the syntax or format of the goal models is not specified, making it hard to assess the generality of the approach.
- When describing the use of few-shot examples for unit test generation, the paper fails to clearly explain how these examples are composed to create tests tailored to the target application and what the expected granularity of the generated unit tests is. Additionally, it should be explicitly stated that the current prototype is Python-specific.
Overall, the paper presents an interesting idea but requires improving clarity and explanation of the technical details to convey its contribution.
- ### [[REVIEWS/Notes]]
- ### YELLOW CONCERNS
background-color:: yellow
- {{query (and [[ffd400]] [[MDE_Intelligence_2025_paper_15]] )}}
collapsed:: true
- ### ❓️Questions
- {{query (and [[question]] [[MDE_Intelligence_2025_paper_15]] )[[question]]}}
query-table:: true
query-properties:: [:block]