<br><br><div class="gmail_quote">On Thu, Mar 17, 2011 at 10:29 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hello all.<br>
<br>
Our next plan is to extend the Hudson build jobs with tests which are<br>
run after VM has built.<br>
<br>
I'd like to ask, what kind of tests we should run for VMs.<br>
<br>
So, here's my questions:<br>
<br>
- do we need a VM specific tests? Or we just use ordinal tests which<br>
are in image(s) by default?<br></blockquote><div><br></div><div>SOme of the standard tests in the Squeak 4.2 suite are specifically for VM stuff. The entire suite depends on the VM in some way. It seems straight-forward to include tests for specific pieces of functionality, for example the mirror primitives, cannotInterpret: and objects-as-methods. Adding tests that test new VM functionality is clearly more than a good idea; it should be de rigueur.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- in case if we need to run VM-specific tests, is they are available<br>
somewhere or not? do we need to create separate package/repository for<br>
holding them?<br></blockquote><div><br></div><div>Check out a 4.2 image and look at the tests. The organization might not be perfect but it's there.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
i'd like to brainstorm that a bit. And then we will do that.<br>
<font color="#888888"><br>
<br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
</font></blockquote></div><br>