Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Xtext Release Engineering"

(New page: = Xtext build server = '''This documentation relates to Xtext version 2 which is currently under development. For Xtext shipped with oAW consult sourceforge.org''' == Build FAQ == == Te...)
 
(Test FAQ)
Line 10: Line 10:
  
 
* Name your plug-in like
 
* Name your plug-in like
 +
 +
<plugin-to-be-tested>.tests
 +
 +
* Generate a test suite, e.g. by running the ''Xtext Tools->Create Test Suite'' action, provided by ''org.eclipse.xtext.testcollector''. Make sure the test suite is in an exported package.
 +
 +
* Add file ''test.xml'' and add it to the binary build by checking it in the ''build.properties'' editor
 +
  Copy the contents form an existing test project and adapt plug-in name and classname. There are two kinds of tests:
 +
** ''ui-test'' plug-in test needing a workbench
 +
** ''core-test'' headless plug-in test

Revision as of 05:26, 23 July 2008

Xtext build server

This documentation relates to Xtext version 2 which is currently under development. For Xtext shipped with oAW consult sourceforge.org

Build FAQ

Test FAQ

How do I add a test plug-in

  • Name your plug-in like
<plugin-to-be-tested>.tests
  • Generate a test suite, e.g. by running the Xtext Tools->Create Test Suite action, provided by org.eclipse.xtext.testcollector. Make sure the test suite is in an exported package.
  • Add file test.xml and add it to the binary build by checking it in the build.properties editor
 Copy the contents form an existing test project and adapt plug-in name and classname. There are two kinds of tests:
    • ui-test plug-in test needing a workbench
    • core-test headless plug-in test

Back to the top