Skip to main content
Jump to: navigation, search

EDT:Running Tests

Revision as of 11:29, 10 January 2013 by (Talk | contribs) (

Running the EDT Tests


This project holds JUnit tests that are designed to test the part binding, validation and IR serialization phase (no generation is performed). To run these tests:

  • Load the project (org.eclipse.edt.tests.validation).
  • Right click on the project in the Project Explorer Or Navigator and select "Run as -> JUnit test".
  • All tests should run with no errors or failures.


This contains a large number of tests that use the EUnit framework (see to test our core language features. To run this test:

  • Load the project (org.eclipse.edt.eunit.test).
  • Set up the compiler(s) you wish to use for the project. To do this, right click on the project in the Project Explorer and select properties. Then click on "EGL Compiler" on the properties page. Select the Java and/or JavaScript generator, depending on what is being tested and press OK.
  • Once compilation completes, right click on the project and select "Generate EGL Test Driver". Select either Java or JavaScript (depending on which environment you are testing).
  • After the test driver is generated, you can run the tests. Refer to and the subsequent sections on how to run the tests and view the results.


This project is made up of 2 projects:


This contains an EUnit test suite. To run the tests:



To run the tests in this project, you will need to first create a "Web 2.0 Client Application with Services" project to ensure that the widget projects are imported into the workspace.

This project is made up of multiple projects:

This project contains an EUnit test suite. To run the tests:

  • Load the project from the containing project
  • Select the project and generate the EGL test driver for "JavaScript Asynchronize"
  • Add the project "" to the java build path of the newly generated project
  • Open the file name RunAllTests_rui.egl in the EGL Rick UI Editor.
  • To test the dedicated services:
  • To test the non-deployed services:

Back to the top