blob: 7798e7086b3ac0e2aa592150929d8b6dc33dc894 [file] [log] [blame]
<br></br>
<html>
<head>
<style type="text/css" title="text/css" media="screen">
td {
border-top: 1px solid #D4D4DD;
text-align: left;
vertical-align: top;
font-weight: normal;
padding: 5pt;
width: 425px;
}
td.entry_cell {
font-weight: bold;
width: 30%
}
td.change {
font-style: italic;
color: red;
}
table {
border-top-style: none;
border-collapse: collapse;
}
h2 {
border-bottom: none;
}
img {
max-width: 425px;
}
</style>
</head>
<body>
<div id="topmain">
<div id="right">
<h2>
Were you looking for:</h2>
<ul>
<li><a href="../../Oxygen/Main/new_oxygen.php">What's New for the Oxygen Release?</a></li>
<li><a href="../../Neon/Main/new_neon.php">What's New for the Neon Release?</a></li>
<li><a href="../../Mars/Main/new_mars.php">What's New for the Mars Release?</a></li>
<li><a href="../../Luna/Main/new_luna.php">What's New for the Luna Release?</a></li>
<li><a href="../../Juno/Main/new_juno.php">What's New for the Juno Release?</a></li>
<li><a href="../../Indigo/Main/new_indigo.php">What's New for the Indigo Release?</a></li>
</ul>
</div>
<div id="left">
<br>
<h1>What's new in Jubula in Kepler</h1>
<table>
<tr>
<td class="entry_cell">
Jubula and GUI<i>dancer</i> standalones are feature-identical
</td>
<td>
<p>
The standalone versions for Jubula and GUI<i>dancer</i> now both
contain the same feature set. They only differ in their branding. More
information on the features available in the Jubula Feature and the Standalones is
on the download page. The standalone versions can be downloaded from the
BREDEX <a href="http://testing.bredex.de">Testing Resources Portal</a>.
To access the GUI<i>dancer</i> standalone, a purchase of a support package is required.
</p>
<img alt="GUIdancer and Jubula standalones" src="../images/guidancerJubula.png">
</td>
</tr>
<tr>
<td class="entry_cell">
Eclipse e4 Applications can be tested
</td>
<td>
<p>
It is now possible to test Eclipse e4 applications. Read the information on
adding the RCP-Accessor to ensure that the AUT can be recognized by Jubula.
</p>
</td>
</tr>
<tr>
<td class="entry_cell">
Search scopes are supported
</td>
<td>
<p>
When using the search dialog, you can now decide to search throughout the whole
project, or just the nodes you have selected.
</p>
<img alt="Search Scopes" src="../images/SearchScopes.png">
</td>
</tr>
<tr>
<td class="entry_cell">
HTML reports contain screenshots of errors
</td>
<td>
<p>
When a HTML test result report is produced, it now contains any screenshots taken on failing test steps.
The images can be expanded and contracted by clicking them.
</p>
<img alt="HTML Reports with Screenshots" src="../images/HTMLReport.png">
</td>
</tr>
<tr>
<td class="entry_cell">
New functions available
</td>
<td>
<p>
There are new functions available to access the name of a node, and the comment on a node.
There is also a new function that lets you access a specific cell in a Central Test Data Set.
</p>
</td>
</tr>
<tr>
<td class="entry_cell">
Properties View is more compact
</td>
<td>
<p>
The Properties View now only shows one line per parameter instead of three in previous versions.
</p>
<img alt="Properties View" src="../images/PropertiesView.png">
</td>
</tr>
<tr>
<td class="entry_cell">
Editable state of Properties View is easier to see
</td>
<td>
<p>
The Properties View is a darker grey when disabled, making it easier to see whether changes can be made or not.
</p>
<img alt="Disabled Properties View" src="../images/NonEditablePropertiesView.png">
</td>
</tr>
<tr>
<td class="entry_cell">
Double-click behavior improved in ITE
</td>
<td>
<p>
Double clicking on an item in a browser opens its direct parent, with the item you double-clicked selected.
Double clicking on an item in an editor opens the editor for that item.
</p>
</td>
</tr>
<tr>
<td class="entry_cell">
Support for own text renderers in SWT
</td>
<td>
<p>
You can now use setData(TEST_TESTABLE_TEXT) to make custom renderers readable during a test.
</p>
</td>
</tr>
<tr>
<td class="entry_cell">
Extensions must be updated
</td>
<td>
<p>
Due to wide-reaching changes in the remote control code, any extensions for versions older than Kepler must be updated.
If you have already updated your extensions for the standalone version 2.0, then this is sufficient.
</p>
</td>
</tr>
</table>
<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&query_format=advanced&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&product=Jubula&target_milestone=2.0&target_milestone=Kepler">Fixed Bugs for Kepler</a></h2>
</div>
</div>