A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit <a rel="external noopener" href="http://www.st.ewi.tudelft.nl/~zaidman/publications/greilerMSR2013.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
Strategies for avoiding text fixture smells during software evolution
<span title="">2013</span>
<i title="IEEE">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/vjelrzmdcvaydenhyicylh7bwa" style="color: black;">2013 10th Working Conference on Mining Software Repositories (MSR)</a>
</i>
An important challenge in creating automated tests is how to design test fixtures, i.e., the setup code that initializes the system under test before actual automated testing can start. Test designers have to choose between different approaches for the setup, trading off maintenance overhead with slow test execution. Over time, test code quality can erode and test smells can develop, such as the occurrence of overly general fixtures, obscure inline code and dead fields. In this paper, we
<span class="external-identifiers">
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/msr.2013.6624053">doi:10.1109/msr.2013.6624053</a>
<a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/msr/GreilerZDS13.html">dblp:conf/msr/GreilerZDS13</a>
<a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/fypukjiiwjdo3kg3h6per2zbn4">fatcat:fypukjiiwjdo3kg3h6per2zbn4</a>
</span>
more »
... gate how fixture-related test smells evolve over time by analyzing several thousand revisions of five open source systems. Our findings indicate that setup management strategies strongly influence the types of test fixture smells that emerge in code, and that several types of fixture smells often emerge at the same time. Based on this information, we recommend important guidelines for setup strategies, and suggest how tool support can be improved to help in both avoiding the emergence of such smells as well as how to refactor code when test smells do appear.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20170810140859/http://www.st.ewi.tudelft.nl/~zaidman/publications/greilerMSR2013.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext">
<button class="ui simple right pointing dropdown compact black labeled icon button serp-button">
<i class="icon ia-icon"></i>
Web Archive
[PDF]
<div class="menu fulltext-thumbnail">
<img src="https://blobs.fatcat.wiki/thumbnail/pdf/be/99/be99f7344ecf238c9632d1d4bf29bdcc454cc213.180px.jpg" alt="fulltext thumbnail" loading="lazy">
</div>
</button>
</a>
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/msr.2013.6624053">
<button class="ui left aligned compact blue labeled icon button serp-button">
<i class="external alternate icon"></i>
ieee.com
</button>
</a>