Difference between revisions of "WTP/Build/WTP Adding JUnits"

From Eclipsepedia

< WTP‎ | Build
Jump to: navigation, search
(WTP test.xml file)
(WTP test.xml file - removed need. See Bug 295153 - Can streamline unit test scripts)
Line 21: Line 21:
 
</ol>
 
</ol>
  
== WTP test.xml file ==
 
  
'''Note:  The test.xml file can be found under the releng.wtpbuilder/distribution directory for the project that you are adding the test for.  i.e. releng.wtpbuilder/distribution/xsl'''
 
 
# there is a test.xml file in wtpBuilder that needs updating. Check two spots in that file.
 
:* one is that the target needs to be defined in top part of file or else the plugin included in another existing target, if there is a "family" of tests).
 
:* Then near the bottom the "all" target must be updated to run the test target (unless the new one was just included in an existing one).
 
  
  
 
[[Category:WTP Build Related| ]]
 
[[Category:WTP Build Related| ]]

Revision as of 01:19, 15 November 2009

How To Add a JUnit Project To the WTP Builds

NORMAL (nearly) PROJECT CREATION

  1. put in cvs
    directory should be created first, creating a folder in the 'tests' directory of the component. Then use eclipse wizard to 'share', but don't use default name (that would create a top level project directory) but instead use the 'browse' function to put in the folder created.
  2. add to appropriate .map file (using the project name, and full cvs name).
    it must be added "by hand" to a map file before it can be released with release tool.
  3. add the project to a features xml file.
    NOTE: For test plugins, the test plugin should NOT be packed (there are some ant tasks that use file functions). And, this means to omit the unpack attribute in the feature.xml file.
  4. (optional) send note to webmaster to have project and its location added to the modules file in CVS, if desired

PROJECT test.xml file

  1. copy a test.xml file from another project, or use this example from the sse.core test suite and edit the 3 or 4 things that are project specific:
    • plugin name
    • main classname that runs all the tests
    • type type of test, either
      • target="core-test" (if there is no UI required), or
      • target="ui-test" (if there is UI required).
  2. add the test.xml file (using check box in properties editor) to the build.properties file so it'll be included in the "bin" build.