On Thu, Oct 10, 2002 at 01:06:05PM -0700, Tom Lord wrote:
> 1) Build a public testing infrastructure.
>
> A public testing infrastructure consists of:
>
> 1) Software standards for configure/build/test tools
> 2) Internet protocol standards for scheduling tests,
> delivering source code to test servers, and retrieving
> results.
> 3) Public servers, implementing those protocols.
> 4) Implementation of these standards for critical projects.
I'd like to bring up the extremely pre-alpha testing harness, QMTest,
that my employer is developing, in this context. QMTest is presently
only 'a better DejaGNU' except that it isn't even there yet. This is
due to chronic lack of time on the part of the various people working
on it (me and Mark Mitchell). However, the architecture is intended
to cope with all of these things. I would love to get more eyeballs
on what we have now, and possibly a few more hands on the devteam.
> Technically: I would like to find resources sufficient to complete my
> work on software tools essential for the tasks outlined above.
> Currently I have `arch' -- a distributed, modern, lightweight,
> tractable revision control system that is quite far along in its
> development; and `package-framework', an earlier stage project
> focusing on release engineering and tools for testing.
'arch' is not going to be a satisfactory solution for me or an awful
lot of other people, until every last line of shell script goes away.
Put your own code where your mouth is -- come back with a system
written in a language that isn't an enemy of maintainable and portable
code, and I'll take you a *lot* more seriously.
zw
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 10 23:36:34 2002