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
2. Samples: example tests
2.1 Accessing the prepared Project
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
3. Tasks
3.1 Starting and connecting to the AUT Agent
3.1.1 Starting the AUT Agent
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.4 Restarting the ITE
3.2.5 Help system
3.2.6 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.4 Migrating to newer versions of Jubula
3.5 Working with Projects
3.5.1 Creating a new Project
3.5.2 Editing the Project and AUT properties
3.5.3 Reusing (referencing) whole Projects in a Project
3.5.4 Opening Projects
3.5.5 Refreshing Projects
3.5.6 Deleting Projects
3.5.7 Saving a Project as a new Project
3.5.8 Importing Projects
3.5.9 Exporting Projects
3.5.10 Versioning Projects
3.6 Defining applications under test (AUT's )
3.7 Starting and configuring AUT's
3.7.1 Configuring AUT's to be started with Jubula
3.7.2 Starting Java AUT's (Swing, SWT/RCP/GEF) with Jubula
3.7.3 Starting Web AUT's (HTML) with Jubula
3.8 Working with browsers: renaming, deleting, using IDs, multiple browsers
3.8.1 Renaming items in browsers
3.8.2 Deleting items from browsers
3.8.3 Working with IDs for Test Cases and Test Suites
3.8.4 Opening the Test Case Browser multiple times
3.9 Working with editors: opening, adding/deleting/renaming items, commenting, extracting and replacing, reverting changes
3.9.1 Opening items in editors
3.9.2 Adding items to editors
3.9.3 Deleting items from editors
3.9.4 Renaming items in editors
3.9.5 Adding comments to items in editors
3.9.6 Commenting out items in editors
3.9.7 Extracting Test Cases from editors: Refactoring
3.9.8 Replacing Test Cases in editors: Refactoring
3.9.9 Saving Test Cases from an editor as a new Test Case
3.9.10 Reverting changes in an editor
3.10 Working with categories in the browsers and editors
3.10.1 Creating a category
3.10.2 Creating Test Cases , Test Suites and Test Jobs in an existing category
3.11 Working with Test Cases
3.11.1 Creating Test Cases
3.11.2 Creating tests from the library of pre-defined Test Cases
3.11.3 Opening existing Test Cases
3.11.4 Editing Test Cases
3.11.5 Adding and inserting new Test Cases to a Test Case
3.11.6 Moving Test Cases to external Projects
3.12 Working with test data
3.12.1 Data types and entering data for Test Cases
3.12.2 Entering concrete values as data in Test Cases
3.12.3 Using references for data in Test Cases
3.12.4 Using the edit parameters dialog to add, edit and delete references
3.12.5 Using variables as data for Test Cases
3.12.6 Using functions as data for Test Cases
3.12.7 Concatenating (combining) parameters
3.12.8 Viewing and changing data sources for Test Cases
3.12.9 Using central data sets
3.12.10 Using an Excel file as an external data source
3.12.11 Using the Data Sets View to enter data loops and to translate data
3.12.12 Special parameters: empty strings and the escape character
3.12.13 Overwriting data for Test Cases and Test Suites
3.13 Working with component names
3.13.1 Creating new component names
3.13.2 Entering and reassigning component names in the Component Names View
3.13.3 Renaming component names
3.13.4 Merging component names
3.13.5 Deleting unused component names
3.13.6 Understanding the component hierarchy
3.14 Working with Test Suites
3.14.1 Creating a Test Suite
3.14.2 Configuring Test Suites in the Properties View
3.15 Working with Test Jobs to test multiple AUT's
3.15.1 Combining Test Suites into a Test Job
3.15.2 Testing different AUT's in one test run
3.15.3 Creating a new Test Job
3.15.4 Specifying which AUT to test in a Test Job
3.16 Information on Test Steps
3.16.1 Specifying Test Steps
3.16.2 Editing Test Steps
3.17 Working with manual Test Cases
3.17.1 Creating manual tests
3.17.2 Executing and analyzing manual tests
3.18 Object mapping
3.18.1 Object mapping
3.18.2 Working with the Object Mapping Editor
3.18.3 Deleting from the Object Mapping Editor
3.18.4 Collecting components (technical names) from the AUT
3.18.5 Mapping (assigning) collected technical names to component names
3.18.6 Object mapping and AUT changes
3.19 Test execution
3.19.1 Prerequisites for test execution
3.19.2 Starting the AUT
3.19.3 Starting, stopping and pausing Test Suites and Test Jobs
3.19.4 Interactive test analysis
3.19.5 Altering the speed of test execution
3.20 Working with test results
3.20.1 The Test Result View
3.20.2 XML and HTML reports
3.20.3 Working with the Test Result Summary View
3.21 Dealing with errors in tests: Event Handlers
3.21.1 Adding Event Handlers to a Test Case
3.21.2 Event types
3.21.3 Reentry types
3.22 Preferences
3.22.1 Test preferences
3.22.2 AUT Agent preferences
3.22.3 Embedded AUT Agent preferences
3.22.4 Database preferences
3.22.5 Editor preferences
3.22.6 Object mapping preferences
3.22.7 Observation mode preferences
3.22.8 Test result preferences
3.22.9 Importing and exporting Database preferences
3.22.10 Label decoration preferences
3.22.11 Workspace preferences
3.22.12 General/Keys preferences
3.22.13 Help preferences
3.23 Observing Test Cases
3.23.1 Tips and tricks for using the observation mode
3.23.2 Starting observing
3.23.3 Observing tests in Java AUT's
3.24 Working with the Problem View
3.24.1 The Problem View
3.25 Working with the Teststyle guidelines
3.25.1 Activating Teststyle for a Project
3.25.2 Configuring Teststyle for a Project
3.25.3 Working with the Problem View to view and fix Teststyle problems
3.26 Working with Metrics in Jubula
3.27 Adapting the user interface
3.27.1 Moving Browsers, Views and Editors
3.27.2 Resizing in the user interface
3.27.3 Restoring user interface defaults
3.27.4 Changing perspectives
3.28 Searching in Jubula
3.28.1 Searching for and opening the original specification of a Test Case or Test Suite
3.28.2 Searching for places where a Test Case has been used
3.28.3 Searching for places where a component name has been used
3.28.4 Searching for places where a central test data set has been used
3.28.5 Using the search dialog
3.28.6 Using the search result view
3.28.7 Searching for items in editors and browsers
3.28.8 Using filters in Jubula
3.28.9 Other filter options
3.29 Troubleshooting
3.29.1 General help
3.29.2 I can't start the AUT Agent
3.29.3 I can't connect to the AUT Agent
3.29.4 I can't start the AUT
3.29.5 I can't map components in the Object Mapping Mode
3.29.6 I can't execute my Test Suite
3.29.7 My Test Suite failed
3.29.8 My Test Suite failed when using rdesktop
3.29.9 I can't save my editor
3.29.10 Creating a support information package
3.29.11 Log file locations
3.30 Finishing up
3.30.1 Stopping the AUT
3.30.2 Disconnecting from the AUT Agent
3.30.3 Closing Jubula and stopping the AUT Agent
3.30.4 Stopping the AUT Agent
3.31 Using the test executor for testing from the command line
3.31.1 Starting the test executor
3.31.2 Parameters for the test executor
3.31.3 Using the test executor with the embedded Database
3.31.4 Using a configuration file
3.32 Using the dbtool client to import, delete and export from the command line
3.32.1 Starting the dbtool
3.32.2 Parameters for the dbtool
3.33 Using Chronon in Jubula
3.33.1 Using Chronon in Jubula
3.33.2 Using Chronon when testing your AUT
3.34 Launch Configurations
3.34.1 Intro
3.34.2 Requirements
3.34.3 Customizing the Perspective
3.34.4 Starting the AUT
3.34.5 AUT Agent
3.34.6 Additional information for RCP AUT's
3.34.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.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.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.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.2 Using Event Handlers locally for specific Test Cases
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.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.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
section
Copyright BREDEX GmbH 2012. Made available under the Eclipse Public License v1.0.