Functional Testing Release Notes: Bredex GMBH April 15, 2014
Functional Testing Release Notes: Bredex GMBH April 15, 2014
Functional Testing Release Notes: Bredex GMBH April 15, 2014
BREDEX GmbH
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Germany
Tel: +49-531 - 243 30 - 0
Fax: +49-531 - 243 30 - 99
www.bredex.de
Release Notes
This document presents the relevant differences between ver-
sions and updates, and provides an account of any develop-
ments or known issues with the current release.
For up-to-date information on a release, it is worth looking in
the FAQ’s on the website.
The release notes are presented in chronological order, with
the most recent at the beginning of the document.
• When a test has run via testexec, you can now trigger the
reporting to ALM tools manually from the Test Result Sum-
mary View.
• This allows you to add the test results from your continuous
integration tests to your issues, bugs and features in your
ALM system.
• When executing tests via the command line using the tes-
texec tool, you can now choose to use an embedded AUT
Agent for the test.
• This can be used to help you write tests that use the actions
check property or store property.
• In the HTML and XML test result reports, and in the result
reports in the ITE, you can now see the value with which
the component was found when the test was executed.
• You can use actions such as click and check existence (and
other actions on the graphics component level) on these
components.
• You can now use ”show where used” on Test Suites to find
out which Test Jobs they have been reused in.
• You can now press »F3« on any Test Case, Test Suite, or
Test Job to open the specification of that item.
• AUT’s that use the Eclipse Luna platform can also be tested
with the ITE. This was also possible in version 7.2.
Export improved
• You can now configure a delay for the content assist in the
Component Names View.
• In the Preferences (in the Test section, you can enter a delay
in milliseconds. This amount of time will be waited after
each character entry before opening the content assist.
• Log files that get larger than 10MB are now automatically
split and zipped.
• If you close a HTML AUT by closing the browser, the ITE will
correctly notice the closure after 5 seconds (configurable)
and will remove the AUT from the running AUT’s view.
Selenium update
• The table view has been removed from the Object Mapping
Editor.
• The AUT Agent and the ITE now use the current directory
as their working directory on Linux systems.
• There are known issues with starting AUT’s that are using
the multi-window mode on Mac OSX, both in Firefox and
Safari.
• We have removed these combinations from our tests.
• You can now save images from errors in the test directly to
your file system using a new button and the context menu
in the image view.
Changes to dashboard
http://HOSTNAME:PORTNUMBER/dashboard
• You can now also use the next and previous error buttons
for the Test Result View that appears during test execution.
• The search dialog now lets you choose whether you want
to search the whole Project, or just the node(s) you have
selected.
• From the Search Result View, you can now perform a mass
replace of Test Cases.
• If you have searched, e.g. for all places where a Test Case
is reused, and want to replace some or all of those places
with a new Test Case, then you can select the option to
replace the current Test Case references with a new Test
Case reference.
• Users testing Swing and RCP AUT’s now have two new ac-
tions to Prepare an AUT for Termination and to Synchronize
the termination and re-start.
• The name and type of the parameter are in the first col-
umn, and the value (which can usually be edited in the
Properties View is in the second column.
• The background for the whole table is gray, and the color
of the text has been changed from black to gray.
• org.eclipse.jubula.rc.common.tester
in this package the base classes for most of the Tester-
Classes are located. Some toolkit-specific implementations
are in the toolkit bundles named below.
• org.eclipse.jubula.rc.swt.tester
SWT-specific implementation for List, Table, Tree,
Application and Menus
• org.eclipse.jubula.rc.swing.tester
Swing-specific implementation for JList, JTable, JTree,
Application and Menus
• org.eclipse.jubula.rc.swt.tester.adapter
SWT adapter.
• org.eclipse.jubula.rc.swing.tester.adapter
Swing adapter.
• org.eclipse.jubular.rc.common.tester.adapter.interfa
Interfaces for all adapters.
-TC1 [VARIABLE_SET=VAR1;VARIABLE_CHECK=$VAR1]
– Set variable =VARIABLE_SET
– Check variable =VARIABLE_CHECK
-TC1
– Set variable: VAR1
– Check variable:$VAR1
Text field / text area / text pane has been renamed to Text
Component. This is also evident in the abbreviation used
for the unbound modules and the component names. It
has changed from txf to txc.
• All Test Steps that had the status deprecated have also
been removed. You should ensure that you no longer use
deprecated Test Steps before switching to the new version.
• You can start the metric from a Test Result Report and enter
a parameter for the minimum amount of waited time (in
milliseconds) that should be considered.
• The Search Result View displays all the static waits within
the node you selected. They are sorted according to the
action they belong to, and you can see how much time
each type of wait accumulates to over the test.
• You can now open the Test Case Browser multiple times.
• You can designate one Test Case Browser as the main browser.
This browser will be used for actions such as show specifi-
cation etc.
• In the Open Project dialog, you can now identify the se-
lected Project and version number as your default Project.
• You can still enter the workspace and the -dbscheme infor-
mation if you prefer not to use the -dburl parameter.
• In HTML AUT’s, you can now map components that use the
<pre> tag and perform e.g. check text actions on them.
• When you use Chronon with your AUT, you now have two
choices – you can use the integrated Chronon to record
your AUT or you can specify where your Chronon instal-
lation is, thus allowing you to use the Chronon Recording
Server. This is the recommended choice for working in con-
tinuous integration processes.
• Using this Dashboard, you can open and analyze Test Re-
sult Reports in a web browser without having to start GUIdancer,
and over the network.
• Any increase to heap space must now be done for the ITE,
no longer for the AUT Agent, as the handling for reports is
now in the client code.
• You can use this information to see which data were used
for your Test Cases, without having to click through each
individual node in the Test Result View. This can be espe-
cially useful if you have one Test Case that runs multiple
times with different datasets.
• There is a new option in the Test Case Editor and Test Suite
Editor to save selected items as a new Test Case.
• The nodes are not copied, but their references are: the
effect is the same as if you had manually created a new
Test Case and added the Test Cases to it.
• You can use this value later on in the test, or you can com-
pare various values using the actions to compare string val-
ues or compare numeric values.
• One example use case for this new action is to test table
filters. The rowCount of the table can be saved into a vari-
able before filtering, and the rowCount after filtering into
a different variable. The variables can then be compared
with each other to ensure that the second value is less than
the first, for example.
• This does not replace the support for custom Swing ren-
derers that can be changed directly by your developers.
• You can now open the Eclipse Marketplace Client from the
Help menu.
• You can use the Marketplace Client to search for new soft-
ware to install.
• The properties view for test results now shows all test data
as two columns: the parameter name and the value.
Selenium update
• When working with Teststyle, you can now open the Project
properties dialog to see the rule that has been flouted via:
Show Teststyle Rule
from the Problem View.
• You can now also enter the Test Job as a parameter for
the report. The Test Suites in the Test Job are still displayed
individually, however.
Embedded gdagent
• If you are starting your AUT and running your tests on your
local machine, you can now connect to an embedded AUT
Agent directly from the ITE.
• In the Test Case Editor and Test Suite Editor, there is a new
option to replace one or more selected Test Cases with an-
other Test Case from the library.
Progress View
• The autrun application has been moved from its own di-
rectory in the installed version to within the server folder.
The autrun directory no longer exists.
• GUIdancer now lets you run code coverage for Java appli-
cations written in Java 1.5 or higher.
Teststyle
• The Teststyle plugin lets you define guidelines for your Project
and informs you when a guideline is not upheld.
• You can use this ID to refer to the Test Case from exter-
nal systems such as bug-tracking systems or requirements
management systems.
• There are two new reports that can be generated from the
Test Result Summary View.
• The first is a report that shows code coverage for the cho-
sen Test Suites.
• The second is a report that shows any comments written
for unsuccessful Test Suites which can be used as a daily
summary of the test status.
Moved preferences
• The preferences for the test can now be found in the pref-
erence dialog under the option Test.
• If you create your own reports for GUIdancer from this ver-
sion, then you must use version 2.6.1 of the BIRT viewer
and engine. Our reports are created with this version of
BIRT and Eclipse version 3.6.1.
Known issues
OS X: Green borders in AUT "flicker" in Object Mapping
Mode
Information
This release is a patch to fix a problem that occurred in the
unbound modules concrete whereby the tree component had
a false component type. The database and license are the
same as in version 4.3.01105.
• The Mylyn plugin is now available for use within the ITE.
• You can also create your own local tasks, and reduce the
amount of Test Cases visible to only those required for the
current task.
• The ITE has a new editor for managing data centrally for a
Project
• Within the editor, you can add data sets which can then
be referenced in Test Cases.
Referenced Test Case the data being used have come di-
rectly from the original specification of this Test Case.
Local Test Case the data being used were entered for this
Test Case. You can change from local to referenced
test data using the combo box to reset the default value
from the referenced Test Case.
Central test data set the data have come from a central
test data set.
Excel data file an Excel file has been entered as the data
source.
• There are new options to search for items and test data
within a Project.
• The search dialog can be opened from the toolbar and of-
fers searches for:
• The tester can mark the action as passed or failed and can
write comments about the Test Step.
• There is a new mode for the AUT Agent to allow this, the
lenient mode.
Test results
• Test results that are reopened from the Test Result Sum-
mary View now contain complete information about each
Test Step.
• Test results can also be exported from the Test Result Sum-
mary View in HTML and XML format.
• In the Test Result Summary View, you can now enter com-
ments about each test run to document the reason for fail-
ing or passing.
• The Object Mapping Editor has a new view – the split view.
New actions
• The action for selecting a node from a tree now also has
the parameter extend selection so that multiple nodes can
be selected in trees.
• You can now drop Test Cases directly into the editor, with-
out having to place the Test Case before or after another
Test Case in the editor.
Other information
New workspace recommended for 4.3
• Full test result details that are still in the database can now
be opened in the Test Result View from the Test Result
Summary View.
• This lets you review tests that ran overnight directly in the
ITE.
• If so, you can start the migration wizard. You specify which
Projects should be imported into the new database (the
Projects must have been exported from the previous ver-
sion).
• You can now comment out Test Cases and Test Steps in
editors.
• Items that have been commented out are inactive and are
neither validated for Test Suite completeness, nor executed.
• You can now select rows and columns based on their title
and also determine how you want the selection to occur
(equals, matches, simple match, not equals).
• Actions that select items from tables, lists and trees have a
new parameter for mouse button.
• The Test Result Summary View now also has the informa-
tion about how many Test Steps failed in a test run.
• The Test Result Summary View now also has the informa-
tion about whether the details for a test run are still in the
database.
• If the results are still available, then the Test Result View
can be reopened.
• In the Test Result View which opens when you open the
results for a test run from the Test Result Summary View,
you can use two new toolbar buttons to spring to the nex-
t/previous error.
Pause on error
• This can be switched on and off during a test run and al-
lows you to easily stop the test to see what went wrong.
New action
Other information
XML and HTML reports scheduled for removal
Performance improvements
Other information
Compatibility with 4.0
Known issues
Console output for DBTool
• Please be aware that Frames and IFrames are not yet sup-
ported in this new implementation.
• For this, you can use the command gdrun with parameters
for toolkit, AUT ID etc.
• Via this view, you can start Test Suites and stop AUT’s.
• Being able to start multiple AUT’s and the new gdrun com-
mand mean that it is now possible to test multiple AUT’s
(or instances of the same AUT) in one test.
• The test result summaries are shown in the new Test Result
Summary View. You can use this view to sort and filter
your test results.
• From the Test Result Summary View, you can create BIRT
reports of your test runs.
• You can also use a BIRT designer to create your own re-
ports.
Information
Altered XML Scheme for extensions
<componentClass>javax.swing.JComboBox
</componentClass>
<componentClass name="javax.swing.JComboBox"/>
• The commands to start and stop the Agent have also changed.
See the user manual for more details.
New licenses
• Full details about the new support service are in the license
agreement and in the shop.
Alternative classloading
Known issues
Refresh problem in the Component Name Browser when
renaming components in the Object Mapping Editor
• The return default Event Handler in Test Suites does not yet
exist, although this is documented.
Information
New software license version
Windows 7 supported
Other information
Administrator privileges required for configuration tools
and license administrator
Known issues
Selection of multiple SWT list items under Linux
Other information
Fix for GEF figure recognition
• Testers wishing to try out the BETA for Mac support are
invited to do so.
• The license manager cannot run on a Mac system; it must
be installed on a Windows or Linux system.
New actions
• The Object Mapping Editor now has a text filter like the
browsers.
Control decoration
New preferences
Other Information
Coolbars and Toolbars in Eclipse
Whitespaces in commands
• Please bear in mind that strings within the quotes are not
checked for validity.
Keyboard mappings
Known issues
Connecting to the AUT Agent
Exit Code 11
Click in component