This document provides an overview of Jubula, an automated testing tool for Rich Client Platform (RCP) applications. It discusses why testing and test automation are important, and introduces Jubula as a tool that allows writing tests without coding by using a drag-and-drop interface. The document demonstrates Jubula's components, test setup, event handlers, and provides a quick demo and discussion of writing tests using Jubula. It also notes some cons of Jubula, such as limitations of regular expressions and database issues, before concluding with references for further information.

1. Functional Test Automation Of RCP With Eclipse Jubula
(Meet the Maned Owl Testing Tool)
-Rajesh

2. Acceptance testing(Early Stage)
(After-break wake-up Call)
Why do we test?
 Quality info close to development
 User perspective at forefront
 Time to react
 To check whether system meets functional,
performance , reliability , security , usability and so
on
Why do we automate
tests?
 To avoid repetitive and boring
manual testing.
 Greater test coverage
 Decrease the time for Testing

3. Agenda
‣ What is Jubula?
‣ Why Jubula and how it is different?
‣ Introduction and Setup
‣ What is even handler in Jubula?
‣ Quick Overview and Short Demo
‣ Test execution using autrun and testexec
‣ Test execution using java code in Junit runner(solving Tower of Hanoi)
‣ Cons in Jubula

4. What is Jubula?
‣ Named After a owl called Jubula letti (Maned Owl)
‣ The Jubula project was born at the end of 2010 to deal with the task of
acceptance test automation and was created from around 85 % of the
code from BREDEX’s commercial testing tool, GUIdancer, which won
the Eclipse Award for the Best Commercial Developer Tool in spring
2010.
‣ Recent Version of Jubula 3.1 is a part of Mars Release Train.
‣ Provides Automation Testing for RCP application and targeted
audience are non developer .

5. Writing test Cases in Jubula is a piece of
Cake

6. Why Jubula?
‣ Treats the software as black-box.
‣ No coding effort is required to write tests ,saving time.
‣ Can create test case that are resistant to the changes in the Ui
‣ Drag and drop test specification from test libraries provided.
‣ Code coverage and mylyn Integration.
‣ Bridging the gap between tester and developer (Writing test cases in
java code)

7. Why Jubula different?
‣ Can start writing the test cases before tool is available.
‣ No coding effort
‣ No relative coordinate based clicking (Clicked based on object
Mapping)
‣ Tests fit better in to agile process and support acceptance test driven
development .

8. Jubula Components
ITE
Test
Executor
DB
AUT Agent
AUT

9. Test setup & Demo

10. About Event Handlers
‣ React to errors
‣ Action error
‣ Component not found
‣ Check failed
‣ Configuration error
Continue test
 Continue
 Exit
 Return
 Retry
 Break
 Pause

11. Why do we need event handlers?
‣ What if unexpected error occurred?
Setup
Workflow
Teardown
Setup
Workflow
Teardown

12. Cons Of Jubula
‣ Regular expression: Can only know whether it’s correct or not at
runtime
‣ Embedded database not stable for real time development
‣ Sound knowledge of RCP required for writing extension .
‣ Database report deletion and refreshing takes lots of time
‣ Importing big project (>100 mb) throws heap memory error
‣ No proper Error dialog

13. Questions?

14. Reference
‣ http://www.bredex.de/tags_en/tag/Jubula+Tutorial.html
‣ http://www.eclipse.org/community/eclipse_newsletter/2014/september/
article1.php
‣ http://jmhofer.johoop.de/?p=97

15. Thank you