Testing erlide

We have very little automated tests yet, so testing is mostly a manual thing.

When submitting a patch, if you can’t provide a basic test, please describe in detail how to test it.

Test frameworks

• For Java, we use JUnit. Some related frameworks are evaluated, like mockito, hamcrest and jbehave.
• For Eclipse UI tests, we use SWTBot.
• For Erlang, we use eunit.

There are two kinds of tests:

1. regular JUnit and Erlang tests that don’t require any Eclipse classes. These will run fast.
2. tests that require Eclipse classes. These need to start Eclipse instances, so they will be slower.

Test projects

There are a number of plugin fragment projects (one for each plugin) that should contain testing code for the respective plugin.

Headless testing

We’d like to be able to run all tests headless (i.e. from the command line and without requiring human intervention). Regular JUnit and Erlang tests can be run easily in this mode. Tests requiring code Eclipse classes need support for instantiating a workspace. Those requiring UI need also a X server to be running (in a server environment Xvfb can be used to fake it).

This info is work in progress! See it as notes, not as reference!

Use Xvfb

Xvfb :1 -screen 0 1024x768x24 &

install needed plugins in Eclipse

# use one single row!
java -jar plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar 
-application org.eclipse.equinox.p2.director 
-artifactRepository http://download.eclipse.org/technology/swtbot/galileo/dev-build/update-site 
-metadataRepository http://download.eclipse.org/technology/swtbot/galileo/dev-build/update-site 
-installIU org.eclipse.swtbot.eclipse.feature.group 
-installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group
-installIU org.eclipse.swtbot.ide.feature.group
-consoleLog