On 2/12/2004 9:07 PM, Randy W. Sims wrote: > How about a model that allows people to volunteer when they can (vs > always). Say you have a server. You would be an author-client. You'd say > I have this software that needs to be tested. The server would take it > and mark it available for testing. Then test-clients could log-on (or > more probably set a cron job or login script). The server would say to > clients that login, "Ok, I have these jobs that need testing."
The problem is turn around time. In order for this to be useful, I need to be able to make a change to the code and within the span of five or ten minutes get results back from the system. The distributed testing would be used pretty much like 'make test'. The other problem is I don't see that "always volunteering" is inconvenient. You run a client program that connects to the test server and idles in the background until contacted by the server with work. Then it does an automated build/test with no intervention from the user. No human required. > Actually, why not just setup your own CPAN. Testers can point CPAN++ at > your CPAN server and it's mostly done. You just need a script to drive > CPAN++ for testers to use to make things easier for them. Easy, simple, > and effective if you can get people testing. Turn around time too slow and requires a human. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ <purl> Hey Schwern! honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk!
