[v3dot10] Re: testing packages

[Klaus D. Witzel]

Marcus, Math,

I'd like to suggest adding NewCompiler to the list of packages tested  
against v3dot10. Are there any tests in NewCompiler which are  
intentionally not green resp. can be made green?

Cheers
Klaus

On Sat, 09 Jun 2007 00:27:02 +0200, Ralph Johnson wrote:

> As I've said earlier, I want a system that lets us test packages so
> that we can make sure that when we make a change to the base image, we
> don't break anything.  I've built a system for running those kinds of
> tests and you can see its results at
> http://speedy.cs.uiuc.edu/~johnson/testResults/3.10alpha.7105.html
>
> There are three issues that I'd like to raise.
>
> First, there are lots of failing tests in the base image.  I think
> most of these have to do with the Multiligual bugs that we fixed.  If
> you start with the alpha.7105 image at
> http://ftp.squeak.org/3.10alpha/  and file in Diego's fixes to
> Multilingual at http://bugs.squeak.org/view.php?id=6520 then you
> should be able to open the test runner, run all the tests, and get the
> same results that I got.  Without Diego's fixes, running all tests
> crashes the system.  Fixes are welcome!
>
> Second, the more packages, the better.  Please suggest packages in PU
> that I should use as test cases.  Packages without any tests aren't
> that useful.  It is Ok for packages to have failing tests, but the
> packages shouldn't crash or ask for input. See
> http://wiki.squeak.org/squeak/5987     Note that GamesTests is a
> package that is just tests, but it depends on a package of games so
> when you load it, you load the games that it tests.  This is a good
> way to provide tests when you don't want to always include the tests
> with the application.
>
> Third, I am not committed to this particular testing system.  It is
> just something I threw together, and requires a bit of handholding to
> keep going.  It probably won't run on anybody else's computer without
> some tweaking.  If somebody else wants to write a better one, I would
> be happy.  Otherwise I will eventually turn it into something more
> stable.  Note that what I want is a way to take a proposed image and
> see if it breaks any package.  The most important report is the one at
> http://speedy.cs.uiuc.edu/~johnson/testResults/3.10alpha.7105.html
> For details, you can always build your own image and use TestRunner,
> so it is not so important that the testing system record the details.
>
> -Ralph