V2 testing

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-08-24 04:40:15

Some time ago, V2 supported only gcc on Linux, so I could run all the tests 
myself. Things changed, and it looks I'm no longer able to test all the 
toolsets we have -- I don't even have access to some of them. And one my NT 
box is still dead.

But it's still desirable to run full tests. Even if toolsets work for authors, 
they might have bugs that tests would discover.

So, I wonder if other developers/users can help with the testing. If there's 
enough people, I'll write a Python script which will run tests and report the 
result to me. That script can be run automatically by job scheduler and won't 
require any human intervention.

I'm interested in testers for 
- Sun C++ compiler
- Code Warrior
- gcc, borland, msvc on cygwin
- gcc, borland, msvc on NT 

If you would like to help, you need:
1. Make sure you can run tests manually (instructions below)
2. Post a note to the list

I'll then write a script and post it.

Thanks in advance,
Volodya

The instructions for running tests manually are:
To run the tests you'd need:

- Get the source tree of Boost.Build (located at tools/build in Boost)
- Have Python installed. Version 2.1 is known to work.
Build Boost.Jam. See $boost_build_root/jam_src/index.html for instructions.
- Configure at least one toolset. You can edit site-config.jam or 
user-config.jam to add new toolsets. Or you can create file test-config.jam 
in $boost_build_root/test directory. In this case, site-config.jam and 
user-config.jam will be ignored for testing.

When all is done, you can run the tests with

python test_all.py

which will use the default toolset, or you can specify toolset on the command 
line, for example:

python test_all.py borland

If everything's OK, you'll see a list of passed tests. Otherwise, a failure 
will be reported.