Eclipse RedDeer project is an extensible framework used for development of automated SWT/Eclipse tests which interacts with application’s user interface. RedDeer provides the PageObjects API for comfortable testing of standard SWT (Buttons, Trees..), JFace (UIForms), Workbench (Views, Editors, ..) and Eclipse (Wizards, Preferences,...) components and also allows creating and extending your own components. RedDeer also provides capabilities to work with graphical editors based on GEF or Graphiti.
Eclipse RedDeer is extensively tested on Linux/CentOS platform. Examination of test results in CI environment is easier thanks to capturing screenshots on test failures and collecting Eclipse Platform log.
The easiest way to get started with the code is to create your own fork, then clone your fork and finally add upstream:
$ git clone git@github.com:<you>/reddeer.git
$ cd reddeer
$ git remote add upstream http://github.com/eclipse/reddeer.git
In case that you have the git repo cloned locally, you can build it using maven:
$ mvn clean install
If you just want to build the base and not to run tests, use this:
$ mvn clean install -DskipTests=true
Copy-Paste this URL to Eclipse Help -> Install New Software...:
http://download.eclipse.org/reddeer/releases/latest
Or latest nightly build:
http://download.eclipse.org/reddeer/snapshots
Finish the installation & restart IDE.
Search your repo for path-to-your-git/reddeer/site/repository and paste this path to Eclipse Help -> Install New Software...
- Chat on Eclipse Mattermost RedDeer channel
- Contact us on Mailing List
- Our Homepage
Go through Getting Started guide.
First, if you find any bugs or areas to improve, please open issue on GitHub. In case you would like to implement a patch, note that RedDeer is Eclipse project and you have to have created an account under Eclipse Foundation and signed Eclipse Contributor Agreement. Moreover, if you are making a contributinon within your work position, you should read Eclipse Foundation Legal FAQ.
$ git pull upstream master
$ git checkout -b name-of-our-branch # ideally, branch name should corresponds to reddeer github issue, ie. rd-1699
Implement your changes/patch or bug fix... In any case, it is a best way to verify your changes that you run build with tests before you actually make a pull request.
$ git push origin name-of-your-branch
Then you can generate a pull-request and we will make review, discuss, etc. If code is good enough, it can be merged into master.