<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Functional tests cannot be automated because they are output-driven. One could test them using Selenium or WebTester, however things like HTML5 functional tests are not possible because they rely on browsers implementations.<br>
<br>Regarding local files - it's not what bothers me. I can live with local files, even though I believe that dangling files are a recipe for information loss. Here are two key points which derive from this:<br> - Why not create a configuration for the Hudson build server to fetch specific Monticello packages, by versions? This would eliminate the need to not commit to Monticello while building a version.<br>
- How can we automate the process of testing Seaside via the different platforms? If we have a uniform build process, maybe this can encourage other dialects to maintain their ports to Seaside?<br> - Is the OneClick distribution automated, or is it built manually?<br>
<br>We can make the build process less involved.<br><br>Avi.<br></font></font></font><br><div style="margin: 0pt;" name="sig_d41d8cd98f"></div><div class="gmail_quote">On Sat, Mar 5, 2011 at 7:16 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">2011/3/5 Avi Shefi <<a href="mailto:avishefi@gmail.com">avishefi@gmail.com</a>>:<br>
<div class="im">> Hi there,<br>
> Having watched the build process for the first time, it looks like there are<br>
> some complicated steps involved.<br>
> I have read the MakeRelease document on the Wiki, and I wondered if there's<br>
> room for further improvements/automation ?<br>
<br>
</div>The functional tests are not automated.<br>
<div class="im"><br>
> If there's one issue that particularly captured my attention, it was the<br>
> fact that we had to stop further commits to the repository during the build.<br>
> I'd love to hear your thought about this.<br>
<br>
</div>I just make commits that should not go into the release to a local<br>
file repository. Works fine.<br>
<br>
Cheers<br>
Philippe<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</blockquote></div><br></div>