Treehydra as JS test suite

[David Mandelin]

Taras says JS development has been regularly busting Treehydra lately. A
recent example would be

https://bugzilla.mozilla.org/show_bug.cgi?id=526299

Taras suggested adding Treehydra's unit tests to our regular JS testing.
What do JS devs think of that? Currently, it would require building
Treehydra (including building a patched gcc) and then running 'make
check' in Treehydra.

--
Dave

[Mike Shaver]

I think we need something that doesn't involve building a patched gcc
if people are going to do it. A tinderbox that runs those tests
against tracemonkey is probably the best bang for the buck.

(They could also incrementally add JS or JSAPI tests for bugs we
introduce on them that aren't caught by our JS suite, or the existing
browser/platform test coverage.)

Mike

[Benjamin Smedberg]

On 11/4/09 9:06 PM, Mike Shaver wrote:

> I think we need something that doesn't involve building a patched gcc
> if people are going to do it. A tinderbox that runs those tests
> against tracemonkey is probably the best bang for the buck.

Yes. In fact, I'm planning on hooking up the regular tinderbox builds with
static analysis soon-ish, so you'll get this mostly for free (it will build
single-threaded spidermonkey from the same tree it's testing, I think).

--BDS