<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">On 25 March 2015 at 14:34:53, Sam Phillips (<a href="mailto:sam@samsworldofno.com">sam@samsworldofno.com</a>) wrote:</div> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">I've picked just one of ours (we have 30+). This is
an API endpoint with no UI. 3.5 years development, ~19 contributors
overall, 3011 specs (of which some are integration).
<div><br></div>
<div>One discussion we have occasionally is the merit of removing
unit tests once the initial BDD/TDD is done and replacing with
fewer, broader tests. Like squashing git commits that made sense in
the context of a branch but years later don't mean anything, do
small individual tests still give value when coverage is available
from wider specs? We've not deleted any yet because everything is
fast enough - eg the component above builds in 4 minutes.</div>
<div><br></div>
<div>I'd be interested if anyone else deletes tests later on.</div>
</div>
<div class="gmail_extra"><br></div></div></div></span></blockquote><div><br></div><div>I’m interested in this too. If I say that foo should happen when a new user signs up, then I write my spec, add my feature and everything is great. Some months later I remove this - would people write a spec to say that foo no longer happens or just delete the spec that says that foo should happen. I usually do something approaching the former - I want to be confident that I’ve actually done what I’ve intended, but that feels like an example of what you’re talking about - once i’m confident the feature has been removed, the value of specs saying that it’s not there seems minimal</div><div><br></div><div>Fred</div><div><br></div><div><br></div><br><blockquote type="cite" class="clean_bq"><span><div><div><div class="gmail_extra">
<div class="gmail_quote">On 25 March 2015 at 14:29, Frederick
Cheung <span dir="ltr"><<a href="mailto:frederick.cheung@gmail.com" target="_blank">frederick.cheung@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
5 years, something like 9/10 people total (not all of them still
left), 8500 specs (of which a 100 or so are integration specs).
Many more if you count the ones that have been deleted when the
corresponding functionality was canned (we had about 200 more specs
a month ago, but I’ve been doing some pruning recently)</div>
<div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
<br></div>
<div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
Fred</div>
<div>
<div class="h5"><br>
<br>
<p style="color:#000">On 25 March 2015 at 14:22:12, Tim Cowlishaw
(<a href="mailto:tim@timcowlishaw.co.uk" target="_blank">tim@timcowlishaw.co.uk</a>) wrote:</p>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<div class="h5">
<div dir="ltr"><span>Hi all,</span>
<div><span><br></span></div>
<div><span>I was idly wondering earlier on about how our test
suites change over the life of a project. New features almost
definitely mean more tests, but refactoring (in my experience)
makes some tests redundant, so it's not necessarily a monotonic
increase over time. Therefore, just to satisfy my own curiosity:
(1) How long has your project been in development? (2) How many
people work on it? (3) How many specs / unit tests do you have, and
(4) How many integration / acceptance tests or cukes do you
have?</span></div>
<div><span><br></span></div>
<div><span>I'll go first:</span></div>
<div><span><br></span></div>
<div><span>I've been working on this project since the beginning of
January as the sole developer, and I've currently got 434 specs and
55 cucumber scenarios (with 204 steps).</span></div>
<div><span><br></span></div>
<div><span>(Obviously this is in no way meant to be a scientific
survey. Just idly wondering how others work) </span></div>
<div><span><br></span></div>
<div><span>Cheers!</span></div>
<div><span><br></span></div>
<div><span>Tim</span></div>
<div><span><br></span></div>
</div>
</div>
</div>
<span>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></span></div>
</div>
</blockquote>
</div>
<br>
_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote>
</div>
<br></div>
</div></div></span></blockquote></body></html>