<div dir="ltr">Hi<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 8, 2014 at 1:58 AM, Adam Williamson <span dir="ltr"></span>wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
</div>Well, we'll want to do all sorts of tests that aren't obviously tied to<br>
any specific package. The only kinds of tests it would make sense to<br>
have in packages would be tests that are very tightly associated with<br>
that package, but then we have a whole bunch of other tests stored<br>
somewhere else, and why not just keep the package-specific tests there<br>
too?<br></blockquote><div><br></div><div>Well the advantage of keeping the package specific tests along with the package is that it provides more visible and is more readily accessible compared to tests that is stored somewhere else. If the expectation is that QA is going to maintain them, former is fine but if you want package maintainers to be involved, then a tight association between the specs etc and tests would be a good thing<br>
<br></div><div>Rahul <br></div></div></div></div></div>