The project has been created. Please visit the project page.
The Jubula Functional Testing Tool project is a proposed open source project under the Eclipse Technology Project.
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the Eclipse community. Please send all feedback to the Eclipse Proposals Forum.
However, the introduction of code to acceptance testing has various negative side-effects:
The Jubula functional testing tool is based on the premise that automated acceptance tests are just as important as the project code, and should adhere to the same best practices (modularity, reusability, and readability) without requiring that any code be produced. This places the power of testing in the hands of the testers and improves accessibility for customers who may want to monitor the tests. The code-free approach keeps test maintenance to a minimum and allows acceptance tests to be written from the user perspective. By focusing on how the user will see the software (as a black-box) , the team can gain valuable quality information which often slips through when only JUnit tests are executed.
Test creation in Jubula is achieved using a library of actions which can be combined using drag and drop. This library has been successfully used in diverse projects and already consists of the vast majority of actions necessary to write acceptance tests.
The Jubula library is platform and application independent, which means that test creation can begin before the software is available. This is a must for agile processes, where acceptance tests must be created alongside or even before development. Traditional processes also benefit from the earlier involvement of the test team to clear up misunderstandings more quickly. Working with the Jubula library means that tests can be executed as soon as code is committed – reducing the time spent between introducing an error and catching it via the tests.
Objectives of the Jubula project:
Jubula will provide functional GUI testing support for Java and HTML applications. It will further try to be an anchor point for a broader testing scope including requirements analysis, code coverage of Java applications and test metrics.The initial components will be
Jubala will use EclipseLink as a persistance layer.
It will integrate with JDT and WDT.
It integrates with Mylyn.
It supports testing of SWT, RCP and GEF components. Testing RAP is currently under evaluation.
We will check on how TPTP and Jubula might benefit from each other. There are areas, for instance code coverage, where the tools complement each other. To our knowledge there is no current development in TPTP on GUI tests or other funtional tests.
SWTbot is aiming at programmed jUnit tests and will probably be used mostly by programmers. Jubula on the other hand is focused on non-programmers specifying test scenarios.
BREDEX GmbH is offering code from their commercial tool GUIdancer as the intial contribution. This offering consists of the core functionality of the GUIdancer testing tool owned by BREDEX. The code base consists of 2000+ Java classes with 350,000+ lines of code. Some code developed using third-party libraries or developed under a NDA will be removed prior to the contribution.
BREDEX will continue working on the project. The current development team of the product version will continue working on the Jubula project.
The following individuals are proposed as initial committers to the project:
We welcome additional committers and contributions.
The following Architecture Council members will mentor this project:
The following individuals, organisations, companies and projects have expressed interest in this project:
|Q4 2010||Working on internal changes to make the code base fit for the initial contibution.|
|Q1 2011||Initial Contribution, Parallel IP, Build|
|20-October-2010||Added mentor, fixed typos|
|26-October-2010||added some interested parties, mentioned consideration for RAP testing|
|05-November-2010||added interested parties|
Back to the top