Skip to content
Browse files

Added section about running tests inside Eclipse, on the Setup page.

The well-kept secret of adding `-Dsdtcore.headless` and `-Dsdtcore.notimeouts` is
no longer a secret!
  • Loading branch information...
1 parent 6407800 commit e9282fdeda0e05422647a2d78796e90082de4b23 @dragos dragos committed Mar 27, 2013
Showing with 27 additions and 0 deletions.
  1. BIN src/sphinx/dev/setup/images/setup.png
  2. +27 −0 src/sphinx/dev/setup/setup.rst
BIN src/sphinx/dev/setup/images/setup.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
27 src/sphinx/dev/setup/setup.rst
@@ -146,6 +146,33 @@ happens when you launch the second Eclipse's instance.
Read the rest of the developer documentation to get more insights about the overall architecture.
+Run the test suite inside Eclipse
+You can use the built-in JUnit runner to run or debug the tests inside Eclipse. As for the normal run,
+you need to the *Equinox Weaving Launcher*. In the *Run Configuration* Dialog, create a new configuration
+using the **JUnit Plug-In test with Equinox Weaving**. Make sure you selected the *org.scala-ide.sdt.core.tests*
+project, and choose the test class you want to run (use ```` to run all tests).
+In the **Main** tab make the following adjustments:
+* Choose **Run an application: [No Application] - Headless Mode**.
+The window should look like this:
+.. image:: images/setup.png
+In the **Arguments** tab, make sure to add the following arguments to the VM arguments list:
+.. code-block:: bash
+ -Dsdtcore.headless -Dsdtcore.notimeouts
+The first one tells the IDE to not try to open any windows or dialogs, while the second one disables
+timeouts for certain actions (otherwise, on a slow or overloaded system, the tests might fail simply
+because of a timeout).
Additional information

0 comments on commit e9282fd

Please sign in to comment.
Something went wrong with that request. Please try again.