[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-patch] Parser torture-testing
|
Title: Message
This patch
enables us to use extensive GCC C/C++ testsuites to test CDT
parser.
To apply:
Apply TortureTest.patch as usual; then create
'torture' directory under
org.eclipse.cdt.ui.tests\parser\org\eclipse\cdt\core\parser\resources
and put .cvsignore
file there (basically, just to keep this directory as a placeholder
for testsuites). Create-patch apparently doesn't handle creation of new
directories, so I have to put it separately.
To use:
By default, torture
testing is disabled. To enable it, edit 'TortureTest.properties' in
'org.eclipse.cdt.ui.tests\parser\org\eclipse\cdt\core\parser\resources'. If you
don't have GCC testsuites, it does nothing. Then go and grab your latest version
of GCC testsuites (for instance, ftp://ftp.fu-berlin.de/unix/gnu/gcc/gcc-3.3/gcc-testsuite-3.3.tar.gz).
Unpack testsuites under
org.eclipse.cdt.ui.tests\parser\org\eclipse\cdt\core\parser\resources\torture
or elsewhere, but
then you'll need to modify 'TortureTest.properties'. That's it, you can run
TortureTest in JUnit Plugin mode. Don't run all ui.tests with torture-test
enabled, as apparently it is included several times (anyone knows why?), and
it's A LOT of test cases.
So, for the results (the latest build):
3020
failures out of 6897 testcases - quick parsing disabled;
626
failures out of 6897 testcases - quick parsing
enabled;
Clearly, some work ahead
;)
/Vic
Attachment:
TortureTest.patch
Description: Binary data
Attachment:
cvsignore.tar
Description: Binary data
