*Jubula Team
Jubula User Manual
Contents
1
. Introduction
1
.
1
Comparison to other testing approaches
1
.
1
.
1
Manual Tests
1
.
1
.
2
Programmed Tests
1
.
1
.
3
Recorded Tests
1
.
1
.
4
The Jubula approach
1
.
1
.
5
Early test creation
1
.
1
.
6
Code-free automation
1
.
1
.
7
Manual tester intelligence
1
.
2
How to read this manual
1
.
2
.
1
Layout
1
.
2
.
2
Conventions Used
1
.
2
.
2
.
1
Typesetting Conventions
2
. Samples: example tests
2
.
1
Accessing the prepared Project
2
.
1
.
0
.
1
Result Reports
2
.
2
The structure of the example Project
2
.
2
.
1
The reused Projects
2
.
2
.
2
The categories
2
.
3
Adder Tests
2
.
3
.
1
Sample 1.1: creating a Test Case from Test Steps
2
.
3
.
2
Sample 1.2: creating a Test Case using the library
2
.
3
.
3
Sample 1.3: using Event Handlers
2
.
4
DVD Tool Tests
2
.
4
.
1
Sample 2.1: testing the menu bar and dialog boxes
2
.
4
.
2
Sample 2.2: testing trees
2
.
4
.
3
Sample 2.3: testing tables
2
.
4
.
4
Sample 2.4: testing tabbed panes, lists, combo boxes
2
.
5
Meters Tests
2
.
5
.
1
Sample 5: Tests with the Meters tool
2
.
5
.
1
.
1
Concatenated parameters
3
. Tasks
3
.
1
Starting and connecting to the AUT Agent
3
.
1
.
1
Starting the AUT Agent
3
.
1
.
1
.
1
Windows users
3
.
1
.
1
.
2
Linux users
3
.
1
.
1
.
3
Starting the AUT Agent from the command line: options and parameters
3
.
1
.
2
Connecting to the AUT Agent
3
.
2
Starting the Integrated Test Environment (ITE )
3
.
2
.
1
Windows Users
3
.
2
.
2
Unix Users
3
.
2
.
3
Choosing a workspace
3
.
2
.
3
.
1
Deleting the list of used workspaces
3
.
2
.
4
Help system
3
.
2
.
5
Working with the AUT Agent and client on one machine
3
.
3
Logging into and switching databases
3
.
3
.
1
Logging in to the Database
3
.
3
.
2
Selecting and changing the Database connection
3
.
3
.
3
Migrating to newer versions of the Database
3
.
4
Working with Projects
3
.
4
.
1
Creating a new Project
3
.
4
.
2
Editing the Project and AUT properties
3
.
4
.
2
.
1
Editing general Project properties
3
.
4
.
2
.
2
Changing the toolkit settings for a Project
3
.
4
.
2
.
3
Editing the languages for a Project
3
.
4
.
2
.
4
Editing the AUT's in a Project
3
.
4
.
2
.
5
Duplicating AUT configurations
3
.
4
.
2
.
6
Editing the AUT configurations in a Project
3
.
4
.
3
Reusing (referencing) whole Projects in a Project
3
.
4
.
3
.
1
Changing the version of a reused Project
3
.
4
.
4
Opening Projects
3
.
4
.
5
Refreshing Projects
3
.
4
.
6
Deleting Projects
3
.
4
.
7
Saving a Project as a new Project
3
.
4
.
8
Importing Projects
3
.
4
.
9
Exporting Projects
3
.
4
.
9
.
1
Exporting the currently opened Project
3
.
4
.
9
.
2
Exporting all of the Projects from the database
3
.
4
.
10
Versioning Projects
3
.
5
Starting and configuring AUT's
3
.
5
.
1
Two options to start applications under test (AUT's )
3
.
5
.
2
Defining an AUT
3
.
5
.
3
Configuring AUT's to be started via Jubula
3
.
5
.
3
.
1
Basic AUT configuration
3
.
5
.
3
.
2
Advanced AUT configuration
3
.
5
.
3
.
3
Expert AUT configuration
3
.
5
.
4
Starting AUT's with the
autrun
command
3
.
5
.
4
.
1
Creating an AUT definition from a running AUT
3
.
6
Working with browsers
3
.
6
.
1
Renaming items in browsers
3
.
6
.
2
Deleting items from browsers
3
.
6
.
3
Working with IDs for Test Cases and Test Suites
3
.
6
.
3
.
1
Copying the ID of a Test Case or Test Suite to the clipboard
3
.
6
.
3
.
2
Opening an element based on an ID in the clipboard
3
.
7
Working with editors
3
.
7
.
1
Opening items in editors
3
.
7
.
2
Adding items to editors
3
.
7
.
3
Deleting items from editors
3
.
7
.
4
Renaming items in editors
3
.
7
.
5
Adding comments to items in editors
3
.
7
.
6
Commenting out items in editors
3
.
7
.
7
Extracting Test Cases from editors: Refactoring
3
.
7
.
8
Replacing Test Cases in editors: Refactoring
3
.
7
.
9
Reverting changes in an editor
3
.
8
Working with Test Cases
3
.
8
.
1
Creating Test Cases
3
.
8
.
2
Creating tests from the library of pre-defined Test Cases
3
.
8
.
2
.
1
Using the library to create tests
3
.
8
.
2
.
2
Information about the library
3
.
8
.
2
.
3
Tips and tricks for using the Test Case library
3
.
8
.
3
Opening existing Test Cases
3
.
8
.
4
Editing Test Cases
3
.
8
.
5
Adding and inserting new Test Cases to a Test Case
3
.
8
.
6
Categories for Test Cases
3
.
8
.
7
Moving Test Cases to external Projects
3
.
9
Working with test data
3
.
9
.
1
Data types and entering data for Test Cases
3
.
9
.
2
Entering concrete values as data in Test Cases
3
.
9
.
3
Using references for data in Test Cases
3
.
9
.
4
Using the edit parameters dialog to add, edit and delete references
3
.
9
.
5
Using variables as data for Test Cases
3
.
9
.
5
.
1
Reading and using values (variables) from the AUT
3
.
9
.
5
.
2
Using environment variables in tests
3
.
9
.
5
.
3
Using the Jubula pre-defined test execution variables
3
.
9
.
6
Concatenating (combining) parameters
3
.
9
.
7
Viewing and changing data sources for Test Cases
3
.
9
.
7
.
1
Changing the data source for a Test Case
3
.
9
.
8
Using central data sets
3
.
9
.
8
.
1
Creating and editing central test data sets
3
.
9
.
8
.
2
Deleting central test data sets
3
.
9
.
8
.
3
Adding and modifying parameters for central test data sets
3
.
9
.
8
.
4
Entering data for central test data sets
3
.
9
.
8
.
5
Reusing central test data sets in Test Cases
3
.
9
.
8
.
6
Importing Excel files as central test data
3
.
9
.
9
Using an Excel file as an external data source
3
.
9
.
9
.
1
Configuring the Excel file
3
.
9
.
9
.
2
Using the =TODAY() function in Excel
3
.
9
.
10
Using the Data Sets View to enter data loops and to translate data
3
.
9
.
10
.
1
Data Sets View : adding multiple data sets to a Test Case
3
.
9
.
10
.
2
Data Sets View : translating test data
3
.
9
.
11
Special parameters: empty strings and the escape character
3
.
9
.
12
Overwriting data for Test Cases and Test Suites
3
.
10
Working with component names
3
.
10
.
1
Creating new component names
3
.
10
.
2
Entering and reassigning component names in the Component Names View
3
.
10
.
2
.
1
Propagating component names: writing Test Cases that can test different components in the AUT
3
.
10
.
2
.
2
Changing component names
3
.
10
.
3
Renaming component names
3
.
10
.
4
Merging component names
3
.
10
.
5
Deleting unused component names
3
.
10
.
6
Understanding the component hierarchy
3
.
11
Working with Test Suites
3
.
11
.
1
Creating a Test Suite
3
.
11
.
2
Configuring Test Suites in the Properties View
3
.
12
Working with Test Jobs to test multiple AUT's
3
.
12
.
1
Combining Test Suites into a Test Job
3
.
12
.
2
Testing different AUT's in one test run
3
.
12
.
2
.
1
Testing independently started AUT's
3
.
12
.
2
.
2
Testing AUT's that are launched by other AUT's
3
.
12
.
3
Creating a new Test Job
3
.
12
.
4
Specifying which AUT to test in a Test Job
3
.
13
Information on Test Steps
3
.
13
.
1
Specifying Test Steps
3
.
13
.
2
Editing Test Steps
3
.
14
Working with manual Test Cases
3
.
14
.
1
Creating manual tests
3
.
14
.
2
Executing and analyzing manual tests
3
.
15
Object mapping
3
.
15
.
1
Object mapping
3
.
15
.
2
Working with the Object Mapping Editor
3
.
15
.
2
.
1
Opening the Object Mapping Editor
3
.
15
.
2
.
2
The different views in the Object Mapping Editor
3
.
15
.
2
.
3
Working with categories in the Object Mapping Editor
3
.
15
.
2
.
4
The configuration view in the Object Mapping Editor
3
.
15
.
2
.
5
Refreshing the Object Mapping Editor
3
.
15
.
2
.
6
Finding components in the AUT via the Object Mapping Editor : highlight in AUT
3
.
15
.
3
Deleting from the Object Mapping Editor
3
.
15
.
3
.
1
Removing unused component names from the Object Mapping Editor
3
.
15
.
4
Collecting components (technical names) from the AUT
3
.
15
.
4
.
1
Understanding the colored dots when collecting component names in the Object Mapping Editor
3
.
15
.
5
Mapping (assigning) collected technical names to component names
3
.
15
.
6
Object mapping and AUT changes
3
.
16
Test execution
3
.
16
.
1
Prerequisites for test execution
3
.
16
.
2
Starting the AUT
3
.
16
.
3
Starting, stopping and pausing Test Suites and Test Jobs
3
.
16
.
3
.
1
Starting a Test Suite or a Test Job
3
.
16
.
3
.
2
Stopping a Test Suite or Test Job
3
.
16
.
3
.
3
Pausing a Test Suite or Test Job
3
.
16
.
4
Interactive test analysis
3
.
16
.
4
.
1
Pause on Error
3
.
16
.
4
.
2
Continuing after an error
3
.
16
.
5
Altering the speed of test execution
3
.
17
Working with test results
3
.
17
.
1
The Test Result View
3
.
17
.
2
XML and HTML reports
3
.
17
.
3
Working with the Test Result Summary View
3
.
17
.
3
.
1
Re-opening the test result view for a test run
3
.
17
.
3
.
2
Filtering and sorting in the Test Result Summary View
3
.
17
.
3
.
3
Changing the amount of result summaries shown in the Test Result Summary View
3
.
17
.
3
.
4
Changing the relevance of a test run
3
.
17
.
3
.
5
Refreshing the Test Result Summary View
3
.
17
.
3
.
6
Deleting test runs from the Test Result Summary View
3
.
17
.
3
.
7
Exporting test results from the Test Result Summary View as HTML and XML reports
3
.
17
.
3
.
8
Entering comments for test runs in the Test Result Summary View
3
.
18
Dealing with errors in tests: Event Handlers
3
.
18
.
1
Adding Event Handlers to a Test Case
3
.
18
.
2
Event types
3
.
18
.
3
Reentry types
3
.
19
Preferences
3
.
19
.
1
Test preferences
3
.
19
.
2
AUT Agent preferences
3
.
19
.
3
Embedded AUT Agent preferences
3
.
19
.
4
Database preferences
3
.
19
.
4
.
1
Adding, editing and removing Database configurations
3
.
19
.
5
Editor preferences
3
.
19
.
6
Object mapping preferences
3
.
19
.
7
Observation mode preferences
3
.
19
.
8
Test result preferences
3
.
19
.
9
Importing and exporting Database preferences
3
.
19
.
10
General/Keys preferences
3
.
19
.
11
Help preferences
3
.
20
Observing Test Cases
3
.
20
.
1
Tips and tricks for using the observation mode
3
.
20
.
2
Starting observing
3
.
20
.
3
Observing tests in Java AUT's
3
.
20
.
3
.
1
Actions that cannot be recorded
3
.
20
.
3
.
2
Performing checks in the Java observation mode
3
.
21
Working with the Problem View
3
.
21
.
1
The Problem View
3
.
22
Adapting the user interface
3
.
22
.
1
Moving Browsers, Views and Editors
3
.
22
.
2
Resizing in the user interface
3
.
22
.
3
Restoring user interface defaults
3
.
22
.
4
Changing perspectives
3
.
22
.
4
.
1
Automatically changing perspective
3
.
23
Searching in Jubula
3
.
23
.
1
Searching for and opening the original specification of a Test Case or Test Suite
3
.
23
.
2
Searching for places where a Test Case has been used
3
.
23
.
3
Searching for places where a component name has been used
3
.
23
.
4
Searching for places where a central test data set has been used
3
.
23
.
5
Using the search dialog
3
.
23
.
5
.
1
Searching for keywords (Test Cases , Test Steps , Test Suites , Test Jobs and categories) throughout the Project
3
.
23
.
5
.
2
Searching for test data
3
.
23
.
5
.
3
Searching for files in the workspace
3
.
23
.
6
Using the search result view
3
.
23
.
7
Searching for items in editors and browsers
3
.
23
.
8
Using filters in Jubula
3
.
23
.
8
.
1
Text filters
3
.
23
.
9
Other filter options
3
.
24
Troubleshooting
3
.
24
.
1
General help
3
.
24
.
2
I can't start the AUT Agent
3
.
24
.
3
I can't connect to the AUT Agent
3
.
24
.
4
I can't start the AUT
3
.
24
.
5
I can't map components in the Object Mapping Mode
3
.
24
.
6
I can't execute my Test Suite
3
.
24
.
7
My Test Suite failed
3
.
24
.
8
My Test Suite failed when using
rdesktop
3
.
24
.
9
I can't save my editor
3
.
24
.
10
Creating a support information package
3
.
25
Finishing up
3
.
25
.
1
Stopping the AUT
3
.
25
.
2
Disconnecting from the AUT Agent
3
.
25
.
3
Closing Jubula and stopping the AUT Agent
3
.
25
.
4
Stopping the AUT Agent
3
.
26
Using the test executor for testing from the command line
3
.
26
.
1
Starting
3
.
26
.
2
Parameters
3
.
26
.
3
Using the test executor with the embedded Database
3
.
26
.
4
Configuration Files
3
.
27
Using the dbtool client to import, delete and export from the command line
3
.
27
.
1
Starting the dbtool
3
.
27
.
2
Parameters for the dbtool
3
.
28
Launch Configurations
3
.
28
.
1
Intro
3
.
28
.
2
Requirements
3
.
28
.
3
Customizing the Perspective
3
.
28
.
4
Starting the AUT
3
.
28
.
5
AUT Agent
3
.
28
.
6
Additional information for RCP AUT's
3
.
28
.
6
.
1
Keyboard Layout
3
.
28
.
6
.
2
RCP Remote Control Plug-in
3
.
28
.
7
Common Pitfalls
4
. Toolkit-specific information
4
.
1
Testing Swing AUT's
4
.
1
.
1
Supported Swing AUT's
4
.
1
.
2
Design for testability in Swing
4
.
2
Testing RCP AUT's
4
.
2
.
1
Supported RCP AUT's
4
.
2
.
2
Setting up an RCP AUT for testing
4
.
2
.
3
Keyboard Layouts
4
.
2
.
4
Design for testability in RCP
4
.
2
.
5
Component name generation in RCP
4
.
2
.
6
Best practices for testing RCP AUT's
4
.
3
Testing GEF AUT's
4
.
3
.
1
Testing GEF components
4
.
3
.
2
Using the GEF inspector
4
.
3
.
3
Adding GEF accessibility to your AUT
4
.
3
.
3
.
1
Setting up your Workspace
4
.
3
.
3
.
2
Walkthrough
4
.
3
.
3
.
3
References
4
.
4
Testing HTML AUT's
4
.
4
.
1
Supported HTML AUT's
4
.
4
.
2
Design for testability in HTML AUT's
5
. Best practices
5
.
1
Keyword design - how to structure your tests
5
.
1
.
1
Making Test Cases into reusable keywords
5
.
1
.
1
.
1
General guidelines for keywords
5
.
1
.
1
.
2
The size of keywords
5
.
1
.
1
.
3
Utility modules for keywords
5
.
1
.
2
Data in keywords
5
.
1
.
3
Structuring your use cases and Test Suites
5
.
2
Naming conventions
5
.
2
.
1
Naming conventions for Test Cases
5
.
2
.
2
Naming conventions for component names
5
.
2
.
3
Naming conventions for Test Suites and Test Jobs
5
.
2
.
4
Naming conventions for referenced parameters
5
.
3
Using categories to structure your tests
5
.
3
.
1
Best practices for structuring the Test Case Browser
5
.
3
.
1
.
1
Executable tests
5
.
3
.
1
.
2
Modules
5
.
3
.
2
Best practices for structuring the Object Mapping Editor
5
.
4
Best practices for using Event Handlers to deal with errors
5
.
4
.
1
Structuring global Event Handlers for your test
5
.
4
.
1
.
1
Creating general Event Handlers
5
.
4
.
1
.
2
Adding the Event Handlers to the use case
5
.
4
.
2
Using Event Handlers locally for specific Test Cases
5
.
4
.
2
.
1
Dealing with occasional dialogs
6
. User interface
6
.
1
Perspectives
6
.
1
.
1
The Functional Test Specification Perspective
6
.
1
.
2
The Functional Test Execution Perspective
6
.
1
.
3
The Functional Test Reporting Perspective
6
.
1
.
4
The Jubula workspace perspective
6
.
2
Browsers
6
.
2
.
1
The Test Suite Browser
6
.
2
.
2
The Test Case Browser
6
.
2
.
3
The Component Name Browser
6
.
3
Editors
6
.
3
.
1
Test Case Editor
6
.
3
.
2
Test Suite Editor
6
.
3
.
3
Object Mapping Editor
6
.
3
.
4
Central Test Data Editor
6
.
4
Views
6
.
4
.
1
The Properties View
6
.
4
.
2
The Data Sets View
6
.
4
.
3
The Component Names View
6
.
4
.
4
The Test Result View
6
.
4
.
5
The Problem View
6
.
4
.
6
The search result view
6
.
4
.
7
The Navigator View
6
.
4
.
8
The console
6
.
4
.
9
The Inspector View
6
.
4
.
10
The Test Result Summary View
6
.
4
.
11
The Running AUT's View
6
.
4
.
12
The Image View
6
.
4
.
13
The Progress View
6
.
5
The status bar
7
. Concepts
7
.
1
Overview
7
.
2
Testing with Jubula
7
.
2
.
1
Understanding how Jubula works
7
.
2
.
1
.
1
Actions
7
.
2
.
1
.
2
Test execution
7
.
2
.
2
Standards conformance
7
.
3
Architecture
7
.
3
.
1
ITE
7
.
3
.
2
AUT Agent
7
.
3
.
3
Working with the ITE and AUT Agent on different machines
7
.
4
Database structure
7
.
4
.
1
Supported systems
7
.
4
.
2
Single-user
7
.
4
.
3
Multi-user
7
.
5
Approaches to testing
7
.
5
.
1
Writing modules in advance
7
.
5
.
2
Creating modules from existing Test Cases
7
.
5
.
3
Choosing a method
7
.
6
Test hierarchy
7
.
6
.
1
Test Steps
7
.
6
.
2
Test Cases
7
.
6
.
3
Test Suites
7
.
6
.
4
Test Jobs
7
.
6
.
5
Projects
7
.
7
Reusability
7
.
7
.
0
.
1
Abstract, concrete and toolkit specific components
7
.
8
Multi-lingual testing
7
.
8
.
1
Project and AUT languages
7
.
9
Object mapping
7
.
9
.
1
Component names
7
.
9
.
2
Technical names
7
.
9
.
3
Assigning technical names to component names
7
.
9
.
4
Locating components during test execution
7
.
10
Test execution
7
.
10
.
1
Test Step execution
7
.
11
Observing user actions
7
.
12
Event Handlers
7
.
12
.
1
How Event Handlers work
7
.
12
.
2
Default Event Handlers
7
.
12
.
3
Customized Event Handlers
7
.
13
Extensibility
7
.
14
Summary
8
. Glossary
Index
Copyright BREDEX GmbH 2011. Made available under the Eclipse Public License v1.0.