Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Rejected: [cdt-patch] Automated JUnit test


Andrew is going to work on making this facility work without having to hard code path names.  The idea behind the test is to be able to run it on any source you happen to have on your system (such as proprietary source).  It should run by default, however, on the source checked into CVS when there is no properties file.  Along with that, we'll make the properties file cvsignore so that everyone can have a different one and not accidently check it in.

Checking in test source is tricky from a licensing perspective since it must comply with CPL.  But we'll do the best we can to get a good sampling in there.

Cheers,
Doug Schaefer
Rational Software - IBM Software Group
Ottawa, Ontario, Canada



"Niefer, Andrew" <aniefer@xxxxxxxxxxxx>
Sent by: cdt-patch-admin@xxxxxxxxxxx

04/16/2003 04:35 PM
Please respond to cdt-patch

       
        To:        "'cdt-patch@xxxxxxxxxxx'" <cdt-patch@xxxxxxxxxxx>
        cc:        
        Subject:        [cdt-patch] Automated JUnit test



Attached are the patches for the automated test framework.  Note, that like
John's line number test, this automated test requires the PDE JUnit plugin
and should be run as a "JUnit Plugin Test".

The automated framework will take a directory and for each c/cpp/h file in
it and in its subdirectories, the framework will add a JUnit test to its
testSuite which will parse that file.

The JUnit test will fail if the parse fails or throws an exception.

Filename and line number for each failing test is output to a specified
file.

There is a properties file (AutomatedTest.properties) in which you specify
the following options, which should be customized before running the test:
cppNature = true, means the files will be cpp files, any other value means c
files.
outputFile = Z:\CDT\report.txt, the file to output the results
testDir = Z:\CDT\test, the directory to look for source files in.

-Andrew





#### patch_04.16.03(cdt.ui.tests).txt has been removed from this note on April 17, 2003 by Douglas Schaefer
#### patch_04.16.03(cdt.core).txt has been removed from this note on April 17, 2003 by Douglas Schaefer

Back to the top