<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automated Unit Test Generation for Python · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2007.14049/</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/2007.14049/feed.xml" rel="self" type="application/rss+xml" /><item><title>Automated Unit Test Generation for Python — mentioned by usagitoneko97</title><link>https://news.ycombinator.com/item?id=27356257</link><guid isPermaLink="false">urn:hackerpapers:mention:2007.14049:27356257</guid><pubDate>Tue, 01 Jun 2021 15:42:47 GMT</pubDate><description>&lt;p&gt;Just skimmed through the paper: https://arxiv.org/pdf/2007.14049.pdf, it seems like they are using some sort of heuristically mutating a test suite until it&amp;#x27;s fully branch covered, based on calculating `branch distance` for each predicate. Why isn&amp;#x27;t a SMT solver like Z3-solver being used here to solve for the predicate (generating inputs to evaluate to true/false)? Since it&amp;#x27;s getting so powerful, and python container/dict/string(regex) operation can also be modeled conveniently. And I&amp;#x27;m also wondering, whether there is a return based automatic test generation, that start from the return…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2007.14049/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Automated Unit Test Generation for Python — mentioned by mmmkkaaayy</title><link>https://news.ycombinator.com/item?id=27352786</link><guid isPermaLink="false">urn:hackerpapers:mention:2007.14049:27352786</guid><pubDate>Tue, 01 Jun 2021 11:00:46 GMT</pubDate><description>&lt;p&gt;There wasn&amp;#x27;t much info on the GitHub repo about how it actually works. Here&amp;#x27;s the paper from the authors: https://arxiv.org/abs/2007.14049 From what I gather from the paper, they frame the problem of test generation as a search problem. An evolutionary algorithm randomly mutates a randomly generated test suite. The evolutionary algorithm optimizes for greater branch coverage. Excerpt from the abstract: &amp;quot;Our experiments confirm that evolutionary algorithms can outperform random test generation also in the context of Python, and can even alleviate the problem of absent type information to some…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2007.14049/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Automated Unit Test Generation for Python — mentioned by khimaros</title><link>https://news.ycombinator.com/item?id=27350834</link><guid isPermaLink="false">urn:hackerpapers:mention:2007.14049:27350834</guid><pubDate>Tue, 01 Jun 2021 04:54:47 GMT</pubDate><description>&lt;p&gt;preprint available for those curious about how this works: https://arxiv.org/abs/2007.14049&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2007.14049/"&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>
