Those tests are run automatically when launching mvn clean verify command on the whole platform code, or mvn clean verify -Pbuild-individual-bundles if you're building a subset of Platform. Since adoption of Tycho, some tests have been enabled as part of the integration-test step of the Tycho build, relying on the tycho-surefire-plugin.

- Headless Mode - for running headless core (runtime, osgi, resource) tests.

Here are some important applications to know about:

On the 'Main' tab, select the appropriate application for that test.

Choose the 'JUnit Plug-in Test' category, and click the button to create a new test.

.resources.AutomatedTests - runs all resource tests.

.runtime.AutomatedTests - runs all runtime tests.

.tests.UiTestSuite - runs all UI tests.

Here are some useful suites to know about: Suites from multiple packages are then aggregated into higher level suites. Each test package typically contains a TestSuite class that contains all the tests in that package.

In the Package Explorer, select the test or test suite you want to run.

A test failure on these tests implies that program behaviour is not as expected by the tests.Ĭorrectness tests can be run from within the Eclipse IDE using a 'JUnit Plug-in Test' launch configuration: The majority of automated tests are testing for program correctness.

6.1 Notes on what you should be evaluating on.

2.3 Importing a coverage session in the Eclipse IDE with EclEmma.

2.2 CI builds with JaCoCo and SonarQube.

2.1 Generate JaCoCo coverage data with Maven/Tycho.

Install junit in eclipse