Skip to content
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.

JUnit test extensions

Vlado Pakan edited this page Aug 5, 2014 · 18 revisions

API/Abstract

Implementation(s)

Usage

JUnit test extensions are actions automatically invoked before or after each and every test is run. They should replace using JUnit annotations @After and @Before for actions invoked for every test so there is no need to copy these action to every test source code.

JUnit extensions are implemented via IBeforeTest and IAfterTest extension points defined within org.jboss.reddeer.junit plugin.

These extension points are implemented within org.jboss.reddeer.junit.extension plugin which is installed by org.jboss.reddeer.junit.extension.feature feature. This feature is mandatory and has to be installed in order to be able to use JUnit extensions defined in RedDeer.

Each JUnit Extension can be disabled via setting respective system property

CloseWelcomeScreenExt

Closes Welcome Screen if opened prior test is run. Can be disabled via setting this system property to false

reddeer.close.welcome.screen=false

DoNotDownloadMavenIndexesExt

Disables downloading maven repository indexes at Eclipse startup prior test is run. Can be disabled via setting this system property to false

reddeer.disable.maven.download.repo.index.on.startup=false

CloseAllShellsExt

Closes all opened shells except workbench shell when test is finished. If such a shell is closed finished test will fail but next test will run only workbench shell opened. It's supposed that when test is finished no additional shells should be opened. Can be disabled via setting this system property to false

reddeer.close.shells=false

Clone this wiki locally