Pith

open record

sign in

arxiv: 2412.09360 · v2 · pith:YZ6Q7P33 · submitted 2024-12-12 · cs.SE

Doc2OracLL: Investigating the Impact of Documentation on LLM-based Test Oracle Generation

Reviewed by Pith T0 review T1 audit T2 compute T3 formal T4 kernel pith:YZ6Q7P33record.jsonopen to challenge →

classification cs.SE
keywords codedocumentationtestcommentsgenerationimpactjavadocoracle
0
0 comments X
read the original abstract

Code documentation is a critical aspect of software development, serving as a bridge between human understanding and machine-readable code. Beyond assisting developers in understanding and maintaining code, documentation also plays a critical role in automating various software engineering tasks, such as test oracle generation (TOG). In Java, Javadoc comments provide structured, natural language documentation embedded directly in the source code, typically detailing functionality, usage, parameters, return values, and exceptions. While prior research has utilized Javadoc comments in test oracle generation (TOG), there has not been a thorough investigation into their impact when combined with other contextual information, nor into identifying the most relevant components for generating correct and strong test oracles, or understanding their role in detecting real bugs. In this study, we dive deep into investigating the impact of Javadoc comments on TOG.

This paper has not been read by Pith yet.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Forward citations

Cited by 2 Pith papers

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score.

  1. LogicHunter: Testing LLM Agent Frameworks with an Agentic Oracle

    cs.SE 2026-07 conditional novelty 7.0

    LogicHunter combines specification-driven test generation with a ReAct-based agentic oracle to discover 40 previously unknown bugs in LangChain, LlamaIndex, and CrewAI, achieving 91.17% oracle precision.

  2. Beyond Coverage and Kill Scores: Empirically Measuring Test Suite Behavioural Gaps

    cs.SE 2026-06 unverdicted novelty 6.0

    An empirical study extracts 20,729 expected behaviors from ten Java libraries and finds 17.5% remain untested, independent of line coverage and mutation scores.