RE: [Owasp-input-api-developers] Testing tool/framework and development platform survey

[Christopher T. <ch...@ch...>]

Alex,

>Probably not. I think it'll be a better bet to find one environment
>against which we can test most of these languages and then spit back
>reports about what succeeded and what failed. Not sure there's a need
>for each of us to configure servers to support all (or even most) of
>these languages. It can only get more complex when we introduce DBs into
>the mix, so for the time being I'm going to advocate a central testing
>setup of some sort. Not sure how we'll make it a reality (suggestions
>welcome), but it seems a good way to start.

Interesting idea; I was thinking more along the lines of iterative
code-test-code-test, but your suggestion would work better in an automated
nightly build type of situation.  Sourceforge has compile farms; I don't
know much about them, but maybe we could setup a nightly build from CVS.
The Jakarta projects (and many Apache projects) do that sort of thing, and
there are several tools to help.

Chris