<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>On the risk of coding before testing: An empirical study on LLM-based test generation workflow · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2607.05139/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2607.05139/feed.xml" rel="self" type="application/rss+xml" /><item><title>On the risk of coding before testing: An empirical study on LLM-based test generation workflow — mentioned by paimapi</title><link>https://news.ycombinator.com/item?id=50306713</link><guid isPermaLink="false">urn:hackerpapers:mention:2607.05139:50306713</guid><pubDate>Fri, 30 Oct 2026 16:56:55 GMT</pubDate><description>&lt;p&gt;I think this is actually the opposite in practice. LLMs generate better tests than they are at assessing which tests are effective (and, inferentially, how a system should behave). See: https://arxiv.org/abs/2410.21136 That said, there&amp;#x27;s also research pointing to LLMs encoding existing bugs as test requirements: https://arxiv.org/abs/2607.05139 That CS PHD researcher, Konstantinou, in particular, has written a lot on this: https://arxiv.org/search/cs?searchtype=author&amp;amp;query=Konstant...&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2607.05139/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
