<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://eiffelroom.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>eiffelroom - testing - Comments</title>
 <link>http://eiffelroom.com/tag/testing</link>
 <description>Comments for &quot;testing&quot;</description>
 <language>en</language>
<item>
 <title>Project Automation Book</title>
 <link>http://eiffelroom.com/blog/patrickr/using_an_automatic_build_and_testing_system#comment-292</link>
 <description>&lt;p&gt;This book ( &lt;a href=&quot;http://www.pragmaticprogrammer.com/sk/auto/&quot;&gt;http://www.pragmaticprogrammer.com/sk/auto/&lt;/a&gt; ) talk about this topic and show good examples.&lt;/p&gt;

You can see Buildix ( &lt;a href=&quot;http://buildix.thoughtworks.com/&quot;&gt;http://buildix.thoughtworks.com/&lt;/a&gt; ) an Agile development platform with  &lt;p&gt;1) Subversion for Source Control&lt;/p&gt;

&lt;p&gt;2) Trac for a Wiki, Bug-Tracker and general Project Management&lt;/p&gt;

&lt;p&gt;3) Cruise Control for Continuous Integration&lt;/p&gt;

</description>
 <pubDate>Tue, 17 Jul 2007 09:54:00 -0700</pubDate>
 <dc:creator>jvelilla</dc:creator>
 <guid isPermaLink="false">comment 292 at http://eiffelroom.com</guid>
</item>
<item>
 <title>I basically just followed</title>
 <link>http://eiffelroom.com/blog/patrickr/using_an_automatic_build_and_testing_system#comment-291</link>
 <description>&lt;p&gt;I basically just followed the getting started page from cruisecontrol&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://cruisecontrol.sourceforge.net/gettingstartedsourcedist.html&quot;&gt;http://cruisecontrol.sourceforge.net/gettingstartedsourcedist.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Instead of ant files I simply used bash scripts, our configuration can be found under&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://svn.origo.ethz.ch/origo/core/trunk/examples/cruisecontrol/config.xml&quot;&gt;https://svn.origo.ethz.ch/origo/core/trunk/examples/cruisecontrol/config.xml&lt;/a&gt;&lt;/p&gt;

</description>
 <pubDate>Mon, 16 Jul 2007 07:44:20 -0700</pubDate>
 <dc:creator>patrickr</dc:creator>
 <guid isPermaLink="false">comment 291 at http://eiffelroom.com</guid>
</item>
<item>
 <title>More details</title>
 <link>http://eiffelroom.com/blog/patrickr/using_an_automatic_build_and_testing_system#comment-290</link>
 <description>&lt;p&gt;Do you have a page that goes more in the details of how one would setup such an environment?&lt;/p&gt;

&lt;p&gt;Thanks, Manu&lt;/p&gt;

</description>
 <pubDate>Sun, 15 Jul 2007 16:21:03 -0700</pubDate>
 <dc:creator>manus_eiffel</dc:creator>
 <guid isPermaLink="false">comment 290 at http://eiffelroom.com</guid>
</item>
<item>
 <title>This setup is a great advantage</title>
 <link>http://eiffelroom.com/blog/patrickr/using_an_automatic_build_and_testing_system#comment-288</link>
 <description>&lt;p&gt;I&#039;d just like to add here that this setup proves to be extremely useful in the development of Origo. We detect regressions almost instantly and getting an email after a successful build and test of Origo is always cool. The system even let&#039;s us know how long it took to do a clean build - at the moment a bit more than twenty minutes.&lt;/p&gt;

&lt;p&gt;A similar approach should in my opinion be used for every bigger project.&lt;/p&gt;

</description>
 <pubDate>Fri, 13 Jul 2007 04:54:29 -0700</pubDate>
 <dc:creator>bayt</dc:creator>
 <guid isPermaLink="false">comment 288 at http://eiffelroom.com</guid>
</item>
<item>
 <title>Thanks for the pointer</title>
 <link>http://eiffelroom.com/blog/maverick/fine_tuning_assertion_checking_dynamically#comment-266</link>
 <description>&lt;p&gt;Hi Manu,&lt;/p&gt;

&lt;p&gt;Thanks for the pointer, I&#039;ll ask such question there, from now on.  For this one, though, I don&#039;t think it will be necessary: if you&#039;re positive about the fact that the assertion checking cannot be set up programmatically, all I&#039;ll do is note that it could support some interesting optimization, for example in the case of big automated test batteries.&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;

&lt;p&gt;Simon&lt;/p&gt;

</description>
 <pubDate>Thu, 31 May 2007 18:19:01 -0700</pubDate>
 <dc:creator>maverick</dc:creator>
 <guid isPermaLink="false">comment 266 at http://eiffelroom.com</guid>
</item>
<item>
 <title>More appropriate medium</title>
 <link>http://eiffelroom.com/blog/maverick/fine_tuning_assertion_checking_dynamically#comment-265</link>
 <description>&lt;p&gt;Hi Simon,&lt;/p&gt;

&lt;p&gt;I think those kind of questions are better answered through the &lt;a href=&quot;http://dev.eiffel.com/Mailing_Lists%20&quot;&gt;  mailing lists&lt;/a&gt; rather than in a blog. The answer is that you can specify in the project settings of EiffelStudio which assertions will be monitored during execution, but once it is setup, you cannot change those settings during execution.&lt;/p&gt;

&lt;p&gt;Hope this helps, Manu&lt;/p&gt;

</description>
 <pubDate>Thu, 31 May 2007 12:17:47 -0700</pubDate>
 <dc:creator>manus_eiffel</dc:creator>
 <guid isPermaLink="false">comment 265 at http://eiffelroom.com</guid>
</item>
</channel>
</rss>
