On Jul 29, 2009, at 23:00 , Michael Roberts wrote: > for the moment you don't need to load any project related code. a > simple test server would > 1a) download the latest published core image from inria or > 1b) load all the available updates into the last image downloaded, > save image locally > 2) file in the baseline test code & run the tests (done - see wiki) > 3) publish the results to the wiki
Yes, I think that is a very good plan. It is simple but it is useful. We have had already a couple of automated testing projects that wanted to do too much and then they were never finished. Note also, that we not only need somebody that implements the server but also somebody that maintains it afterwards. Cheers, Adrian > > cheers, > Mike > > 2009/7/29 Simon Denier <[email protected]>: >> Stef is talking of http://www.squeaksource.com/TestServerSimple.html >> Now this is a rather rudimentary adaptation from a tool made by >> Swiss guys. >> It runs automatically when launching the image, loads packages and >> runs >> tests for different projects. >> Right now it is tailored for Moose projects >> I guess that the area that need improvements are: >> - configuration of projects to load, with prerequisites (using >> Metacello >> perhaps?). Right now this is hard-coded, see TSProject class>>run >> - headless running (sometimes some interactive dialogs still pop up, >> especially when there is a problem loading a package, and this >> ruins the >> automatization) >> - better handling of errors (problems such as above) >> >> On 29 juil. 09, at 18:46, Robert Peters wrote: >> >> What is this "testServer" you are talking about? I searched this >> forum a >> little bit but didn't find any information on it. >> >> I write web-apps in Django for Google App Engine, and my current >> test suite >> for a project takes 45 seconds to run. This frustrates me because >> unit >> testing is (or, at least, should be) an easily distributed task (as >> good >> unit tests do not depend on each other). If Python would even >> simply use >> both cores of my main work computer, my tests would only take 23 >> seconds, >> and if it used all computers on my local network, it could take 5-10 >> seconds. This would be a huge saving for me. >> >> All of this to say I have been thinking about a 'test server' that >> would >> take a queue of tests, set up the proper environments on as many >> cores as it >> had available, and send out the tests, collect the responses and >> display >> them. >> >> Is this what you mean by 'testServer'? >> >> I have wanted to help Pharo, but being an un-skilled Smalltalk >> programmer, >> and having other Python-based projects that were more urgent, I >> haven't done >> much about it. However, this 'testServer' caught my eye, because >> I've been >> thinking about creating such a thing for my own Python-based use. >> Please >> let me know if what I propose is what you intend. If so I may be >> willing to >> try and create something for Pharo to use. >> >> Kind regards, >> Robert >> >> >> Stéphane Ducasse-2 wrote: >> >> >> - a nicer project would be to help improving the embryonic testServer >> >> we have >> >> Stef >> >> >> >> -- >> View this message in context: >> http://n2.nabble.com/Beginner-Tasks-tp3187343p3351068.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Simon >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
