<br><br><div class="gmail_quote">On Fri, Mar 18, 2011 at 2:26 AM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@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><br><br><div class="gmail_quote">On Thu, Mar 17, 2011 at 6:21 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">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">
<div><div></div><div><br>
On 18 March 2011 01:30, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Thu, Mar 17, 2011 at 10:29 AM, Igor Stasenko <<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@gmail.com</a>> wrote:<br>
>><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>
><br>
> 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.<br>
><br>
>><br>
>> - 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>
><br>
> Check out a 4.2 image and look at the tests. The organization might not be perfect but it's there.<br>
><br>
<br>
</div></div>You mean non-VM-specific tests, just those which lying in image(s)?<br>
<br>
Yes, that's the first thing which comes into mind. And sure thing for<br>
start it is ok.<br>
<br>
For example, Hudson runs tests for PharoCore1.3 image, each time new<br>
update there.<br>
<a href="https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/" target="_blank">https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/</a><br>
<br>
It is easy to tweak this config and run it using freshly built VM(s),<br>
one per each platform * JIT/Stack/MT configs.<br>
<br>
But i wonder if we may need to be more focused and create some package(s)<br>
to group tests around VM or its individual plugins.<br></blockquote><div><br></div><div>Have you looked, as I suggested, in a Squeak 4.2 image? You'll find Tests-VM, Tests-Finalization, Tests-ObjectsAsMethods </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br></div></blockquote></div></blockquote><div><br><br><br>So maybe we should integrate them in Pharo too ?<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>
<br>
<br>
>><br>
>> i'd like to brainstorm that a bit. And then we will do that.<br>
>><br>
>><br>
>> --<br>
>> Best regards,<br>
>> Igor Stasenko AKA sig.<br>
><br>
<br>
</div>--<br>
<div><div></div><div>Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br>
<br></blockquote></div><br>