David P. Caldwell wrote: > On Jan 16, 4:45 am, Marc Guillemot <[EMAIL PROTECTED]> wrote: >> Attila Szegedi wrote: >> Failed: ../tests/ecma_3/Date/15.9.5.5.js: >> Math.abs(Date.parse(now.toLocaleString()) - now.valueOf()) < 1000 = >> false FAILED! expected: true >> Failed: ../tests/js1_5/Regress/regress-58116.js: FAILED! expected: >> Expected value '-120', Actual value '-60' >> Failed: ../tests/js1_5/Regress/regress-89443.js: JavaScript errors: >> Failed: ../tests/js1_5/Regress/regress-98901.js: JavaScript errors: >> Failed: ../tests/js1_5/extensions/regress-226507.js: JavaScript errors: >> ------------------------------- >> >> In fact I don't really care if these tests are excluded or not but it >> would help if the tests that should pass could be up to date >> (additionally a mechanism to detect tests that already pass even if they >> are marked as excluded would be useful). > > The test driver can help here (without resorting to grep) -- it emits > the results in HTML format (easier to browse) and also in XML format > (easier to postprocess). Running the suite with -f myfile.html will > create two files -- myfile.html and myfile.html.xml containing data > about what happened. > > You can run the excluded tests (alone) just by loading the list of > tests to run using the -l switch (that's a lowercase "L"), as in -l > @<skip-list-file>.
not really a solution, too much manual work ;-( Cheers, Marc. -- Blog: http://mguillem.wordpress.com _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
