#7 Test/Demo Suite

[Chris Thomas]

I am going to need a group of application tests to demo
off parts of fusion, to show that things work and
perhaps give a sample implemenation of the power of
some parts of fusion.

it would be nice and make it more of a professional
engine, rather than some engine someone make on the net
that has bad support and really bad documentation

[Chris Thomas]

Logged In: YES
user_id=682144

This has started to appear, a testsuite has been added to
the CVS and currently only shows off the Network system, but
it's a start in the right direction

[Chris Thomas]

Logged In: YES
user_id=682144

There needs to be an organised structure in the testsuite,
I'm wondering whether it's clever to have a central binary
directory, or whether they should be spread where projects
are, to also have the binaries there too.

there is an argument for both situations

for centralisation
1. There is a single point where to output files
2. Only have a single copy of Fusion
headers/libraries/binaries for the entire testsuite

against centralisation
1. You have to devise a namespace which can accommodate all
the projects that will eventually end up in the testsuite.
This can be quite hard and might require some scripting to
get it all done right
2. this scripting is platform dependant, so each platform
will require scripts to get certain things done

this is all based on my current frame of mind, which cannot
see another way of handling multiple modules with
installation without some kind of scripting and that
scripting is going to be maintained on all platforms. So it
might be a real problem