Added SR2 pages to Jubula
diff --git a/new/Indigo/Main/new_indigo.html b/new/Indigo/Main/new_indigo.html
new file mode 100644
index 0000000..cbb71ce
--- /dev/null
+++ b/new/Indigo/Main/new_indigo.html
@@ -0,0 +1,193 @@
+<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="left">
+
+<h2>
+Were you looking for:</h2>
+<ul>
+<li><a href="../SR1/new_indigosr1.php">What's New for the Indigo SR1 Release?</a></li>
+<li><a href="../SR2/new_indigosr2.php">What's New for the Indigo SR2 Release?</a>
+</ul>
+<br>
+<br>
+<h1>What's new in Jubula Indigo</h1>
+
+<h2>What's "old"</h2>
+<p>
+The Indigo release for Jubula consists for the most part of the features released with
+the pre-release version, which in turn is almost the same feature-set
+as was in GUI<i>dancer</i> 4.3.
+<br>
+Because of this, everything is new for this first release of Jubula!
+</p>
+
+<h3>A really quick overview of what was in already:</h3>
+
+<ul>
+<li>You can create (automate) tests by dragging and dropping modules from libraries of actions
+installed with Jubula.</li>
+<li>Tests can be automated for AUT's (Applications Under Test) written with Swing, SWT/RCP/GEF and HTML.</li>
+<li>Tests can be executed interactively or via the test executor (e.g. for continuous integration).</li>
+<li>Test results can be viewed directly in the Integrated Test Environment after execution and
+can also be reopened for later analysis, as they are stored in the database.</li>
+<li>Errors in the test are recorded automatically as screenshots and can be dealt with using "Event Handlers".</li>
+<li>There are various options for searching, categorizing and filtering to make working with Jubula more
+comfortable.</li>
+</ul>
+<p>
+The best thing to do to find out more is to read the documentation and do the cheat sheets
+to see what you can do with the tool.
+
+Look at the <a href="../../../documentation.php">documentation</a> page for more details.
+</p>
+
+<h2>What's new</h2>
+
+<table>
+<tr>
+ <td class="entry_cell">
+ Interactive test analysis:<br>
+ Continue without Event Handler
+ </td>
+ <td>
+ <p>
+ When running tests from the Integrated Test Environment (ITE), you could
+ already globally opt to pause the test execution if any errors occur. Using
+ the new "continue without Event Handler" button on the toolbar,
+ you can specify on an error-for-error basis
+ whether to execute an Event Handler for the error or whether to continue the test
+ <i>as if</i> no error had occured.
+ <br>
+ This lets you get a quick overview of the status of the whole test without having to
+ restart the execution / reset the application after each error.
+ </p>
+ <img alt="Continue without Event Handler" src="../images/ContinueWithoutEH.png">
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">
+ Copy ID to clipboard and Open Test Case from ID
+ </td>
+ <td>
+ <p>
+ To allow a light integration with external systems, the unique ID for a Test Case
+ can now be copied to the clipboard. An ID already in the clipboard can be used to open a Test
+ Case using the key combination Shift+F9.
+ </p>
+ <img alt="Copy ID to clipboard" src="../images/CopyID.png">
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">Database configuration</td>
+ <td>
+ <p>
+ Database configuration is now a part of the preferences. The default database
+ is the embedded (H2) database. Other databases can be added via the database preference
+ page.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">Test execution speed</td>
+ <td>
+ <p>
+ We have significantly increased the speed at which tests are executed.
+ Use the <i>Step Delay</i> field in the Properties View for a Test Suite
+ to set a global delay between executed steps to make watching a test easier.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">Added support for components</td>
+ <td>
+ <p>
+ Div containers and lists in HTML applications are now supported. <br>
+ The SWT components <i>slider, date and time, spinner</i> and <i>scale</i>
+ are now supported as <i>Graphics Components</i> (i.e. they can be mapped, clicked and
+ checked for existence, focus and various properties).
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">HTML ID Attribute Name</td>
+ <td>
+ <p>
+ In the AUT configuration, you can now specify an attribute name which will be
+ use to identify components in the HTML AUT.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">Renaming and restructuring</td>
+ <td>
+ <p>
+ The perspective names and some names for components have changed. The options to
+ open, import, export and delete projects are now in the "Test" menu <i>not in the "File" menu</i>,
+ and the preferences are now under the topic "Test".
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="entry_cell">Migrating from GUI<i>dancer</i> 4.3 to Jubula</td>
+ <td>
+ <p>
+ Read the Installation Manual for information on migrating from a 4.3 database to
+ the new database scheme. Any existing extensions must also be migrated:
+ </p>
+ <ul>
+ <li>The package names have changed from <i>com.bredexsw.guidancer</i> to
+ <i>org.eclipse.jubula</i></li>
+ <li>The class prefix name GD has been replaced by JB</li>
+ <li>Client and server (RC) files must be adapted and recompiled with the new Jar files.</li>
+ </ul>
+ </td>
+ </tr>
+
+</table>
+
+<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?chfieldto=2011-06-10;query_format=advanced;chfield=bug_status;bug_status=RESOLVED;bug_status=CLOSED;classification=Technology;product=Jubula">Fixed Bugs for Indigo</a></h2>
+
+</div>
+
+</div>
\ No newline at end of file
diff --git a/new/Indigo/Main/new_indigo.php b/new/Indigo/Main/new_indigo.php
new file mode 100644
index 0000000..1e1354f
--- /dev/null
+++ b/new/Indigo/Main/new_indigo.php
@@ -0,0 +1,29 @@
+<?php
+/*******************************************************************************
+ * Copyright (c) 2009 Eclipse Foundation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ *
+ *******************************************************************************/
+
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
+ $App = new App();
+ $Nav = null;
+ $Menu = new Menu();
+ include($App->getProjectCommon());
+
+ $pageTitle = "New: Indigo";
+ $theme = "Nova";
+
+ $html = file_get_contents('new_indigo.html');
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
\ No newline at end of file
diff --git a/new/Indigo/SR1/new_indigosr1.html b/new/Indigo/SR1/new_indigosr1.html
new file mode 100644
index 0000000..f6f5dfc
--- /dev/null
+++ b/new/Indigo/SR1/new_indigosr1.html
@@ -0,0 +1,260 @@
+<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="left">
+<h2>Were you looking for:</h2>
+<ul>
+<li><a href="../Main/new_indigo.php">What's New for the Indigo Release?</a></li>
+<li><a href="../SR2/new_indigosr2.php">What's New for the Indigo SR2 Release?</a>
+</ul>
+
+<br>
+<br>
+<h1>What's new in Jubula in Indigo SR1</h1>
+
+<table>
+<tr>
+ <td class="entry_cell">
+ <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node39.html">
+ Embedded AUT Agent</a>
+ </td>
+ <td>
+ <p>
+ 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. This saves you
+ having to start an Agent on localhost. This is also useful for testers working with
+ Jubula as a feature in an Eclipse installation. The embedded AUT Agent is started
+ on port 60000 by default; this number can be changed in the preferences.
+ </p>
+ <img alt="Embedded AUT Agent" src="../images/EmbeddedAgent.png">
+ </td>
+ </tr>
+
+<tr>
+ <td class="entry_cell">
+ AUT Agent now part of the Jubula feature
+ </td>
+ <td>
+ <p>
+ There is now no need to use the AUT Agent from the standalone version of Jubula to be
+ able to work with Jubula as a feature: The AUT Agent is now included in the
+ distribution.
+ </p>
+ <img>
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node266.html">
+ Launch configurations</a> for Swing and RCP AUT's
+ </td>
+ <td>
+ <p>
+ When working with the Jubula feature, you can now start your AUT from
+ within the IDE as a launch configuration. This is available for Swing
+ and RCP AUT's.
+ </p>
+ <img>
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ Object Mapping Editor: <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node169.html">
+ Cleanup unused component names </a>
+ </td>
+ <td>
+ <p>
+ In the Object Mapping Editor, there is a new option in the context-sensitive
+ menu. Via <b>Cleanup -> unused component names</b> you can start a search for
+ any component names that are no longer used in Test Suites for this AUT. Once the
+ search is finished, you can delete all of these unused names from the Object
+ Mapping Editor. If they are then no longer used in the entire Project, they
+ can be deleted from the Component Names Browser.
+ </p>
+ <img alt="Delete Unused Component Names" src="../images/DeleteUnusedCompNames.png">
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ HTML Test Result Reports can be expanded again
+ </td>
+ <td>
+ <p>
+ Following changes made for the initial contribution, the HTML Test Result Reports
+ could not be viewed properly in the previous version. In this release, the nodes
+ in the HTML reports can be expanded and collapsed to view the whole test progress.
+ </p>
+ <img alt="HTML Report" src="../images/HTMLReport.png">
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node171.html">
+ State of component recognition</a> displayed when collecting technical names
+ </td>
+ <td>
+ <p>
+ When a component (technical name) is collected from an AUT, it receives a colored
+ dot corresponding to the accuracy of the object recognition for this component
+ <i>at the time of collecting</i>. A <b>green</b> dot signifies that the component
+ could be found with an exact match, and was the only component above the threshold.
+ A <b>yellow</b> dot means that the component is an exact match, but that multiple
+ other components were also above the threshold. A <b>red</b> dot means that this component
+ cannot be relocated in the current state of the application.
+ </p>
+ <img alt="Object Mapping Colors" src="../images/ColorDot.png">
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ Migration wizard re-enabled
+ </td>
+ <td>
+ <p>
+ When migrating between the Indigo release and SR1, the migration assistant
+ will automatically notify you that your database scheme is out-of-date.
+ You can then select which Projects to import (these must have been exported
+ from the database prior to migrating!).The assistant will drop the tables in the
+ database, recreate the necessary tables and import the Projects you specified.
+ </p>
+ <img alt="Database Migration" src="../images/Migration.png">
+ </td>
+</tr>
+<tr>
+
+<td class="entry_cell">
+ Refactor: <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node94.html">
+ Replace with Test Case</a>
+ </td>
+ <td>
+ <p>
+ In the Test Case Editor and Test Suite Editor, there is a new option to replace one or more
+ selected Test Cases with another Test Case from the library.
+ A new wizard takes you step-by-step through the replacement process,
+ letting you transfer component names and add further information for the new Test Case.
+ This feature should help testers who want to restructure their tests
+ after creating a reusable module to replace one or more Test Cases.
+ </p>
+ <img alt="Replace with Test Case" src="../images/ReplaceTC.png">
+ </td>
+</tr>
+
+<tr>
+ <td class="entry_cell">
+ <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node83.html">
+ Copy ID to clipboard</a> also for Test Suites
+ </td>
+ <td>
+ <p>
+ The ability to copy a unique ID to the clipboard to reference a Jubula element
+ in external systems has also been implemented for Test Suites.
+ You can now copy the ID of a Test Case or a Test Suite to the clipboard,
+ and also open an element based on its ID in the clipboard using <b>Shift+F9</b>.
+ </p>
+ <img alt="Copy ID to Clipboard" src="../images/CopyIDTS.png">
+ </td>
+</tr>
+
+<tr>
+ <td class="entry_cell">
+ The DBTool is more verbose
+ </td>
+ <td>
+ <p>
+ The command line tool to import, export and delete Projects in the
+ database, the DBTool, has been updated so that it is more verbose.
+ </p>
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ Progress View
+ </td>
+ <td>
+ <p>
+ The ITE now uses the progress view to show longer-running activities such as
+ test execution, connecting to AUTs etc.
+ </p>
+ <img>
+ </td>
+</tr>
+<tr>
+ <td class="entry_cell">
+ Edit Parameters Dialog in Central Test Data Editor can be opened via double-click
+ </td>
+ <td>
+ <p>
+ In the Central Test Data Editor, it is no longer necessary to open the Edit Parameters
+ Dialog via context-menu, as it can now also be opened via double-click on the data set
+ you wish to edit.
+ </p>
+ </td>
+</tr>
+
+<tr>
+ <td class="entry_cell">
+ Mac keyboards now supported, new mechanism for adding keyboard layout files
+ </td>
+ <td>
+ <p>
+ In the AUT configuration dialog for SWT and RCP AUTs, the Keyboard Layout combo box now only offers
+ layouts that have been defined for Jubula. German (DE) and English (US) are defined as standard.
+ As well as being able to add keyboard layouts for other keyboards,
+ you can also define platform-specific keyboard layouts (e.g. for Mac)
+ The documentation has been updated to describe the new mechanism for adding keyboard layouts.
+ </p>
+ </td>
+</tr>
+
+
+</table>
+
+<h1>Other information for this release</h1>
+<p>
+Read the release notes (available from the <a href="../../../documentation.php">documentation</a> page) for more
+details, including known issues and other important information.
+
+<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=RESOLVED;bug_status=CLOSED;classification=Technology;product=Jubula;target_milestone=Indigo%20SR1">Closed Bugs for Indigo SR1</a></h2>
+</div>
+
+</div>
\ No newline at end of file
diff --git a/new/Indigo/SR1/new_indigosr1.php b/new/Indigo/SR1/new_indigosr1.php
new file mode 100644
index 0000000..a4b8e3a
--- /dev/null
+++ b/new/Indigo/SR1/new_indigosr1.php
@@ -0,0 +1,29 @@
+<?php
+/*******************************************************************************
+ * Copyright (c) 2009 Eclipse Foundation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ *
+ *******************************************************************************/
+
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
+ $App = new App();
+ $Nav = null;
+ $Menu = new Menu();
+ include($App->getProjectCommon());
+
+ $pageTitle = "New: Indigo SR1";
+ $theme = "Nova";
+
+ $html = file_get_contents('new_indigosr1.html');
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
\ No newline at end of file
diff --git a/new/Indigo/SR2/new_indigosr2.html b/new/Indigo/SR2/new_indigosr2.html
new file mode 100644
index 0000000..74ee9ad
--- /dev/null
+++ b/new/Indigo/SR2/new_indigosr2.html
@@ -0,0 +1,71 @@
+<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="left">
+<h2>Were you looking for:</h2>
+<ul>
+<li><a href="../Main/new_indigo.php">What's New for the Indigo Release?</a></li>
+<li><a href="../SR1/new_indigosr1.php">What's New for the Indigo SR1 Release?</a>
+</ul>
+
+<br>
+<br>
+<h1>What's new in Jubula in Indigo SR2</h1>
+
+<p>
+The Indigo SR2 release for Jubula contains no changes to the release for
+<a href="../SR1/new_indigosr1.php">SR1</a>.
+
+</p>
+
+
+<h1>Other information for this release</h1>
+<p>
+Read the latest release notes (available from the <a href="documentation.php">documentation</a> page) for more
+details, including known issues and other important information.
+
+<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED;bug_status=CLOSED;query_format=advanced;list_id=625234;product=Jubula;target_milestone=Indigo%20SR2;classification=Technology">Closed Bugs for Indigo SR2</a></h2>
+
+</div>
+
+</div>
diff --git a/new/Indigo/SR2/new_indigosr2.php b/new/Indigo/SR2/new_indigosr2.php
new file mode 100644
index 0000000..f25a478
--- /dev/null
+++ b/new/Indigo/SR2/new_indigosr2.php
@@ -0,0 +1,29 @@
+<?php
+/*******************************************************************************
+ * Copyright (c) 2009 Eclipse Foundation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ *
+ *******************************************************************************/
+
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
+ $App = new App();
+ $Nav = null;
+ $Menu = new Menu();
+ include($App->getProjectCommon());
+
+ $pageTitle = "New: Indigo SR2";
+ $theme = "Nova";
+
+ $html = file_get_contents('new_indigosr2.html');
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
\ No newline at end of file
diff --git a/new/_index.html b/new/_index.html
index 9957963..cac961d 100644
--- a/new/_index.html
+++ b/new/_index.html
@@ -42,215 +42,39 @@
<div id="topmain">
<div id="left">
-
-<a href="new/Indigo/new_indigo.php">Looking for the What's New for the Indigo Release?</a>
+<h2>
+Were you looking for:</h2>
+<ul>
+<li><a href="new/Indigo/Main/new_indigo.php">What's New for the Indigo Release?</a></li>
+<li><a href="new/Indigo/SR1/new_indigosr1.php">What's New for the Indigo SR1 Release?</a></li>
+</ul>
<br>
<br>
-<h1>What's new in Jubula in Indigo SR1</h1>
+<h1>What's new in Jubula in Indigo SR2</h1>
+<p>
+The Indigo SR2 release for Jubula contains no changes to the release for
+<a href="new/Indigo/SR1/new_indigosr1.php">SR1</a>.
+</p>
-<table>
+<!-- <table>
<tr>
<td class="entry_cell">
- <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node39.html">
- Embedded AUT Agent</a>
</td>
<td>
<p>
- 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. This saves you
- having to start an Agent on localhost. This is also useful for testers working with
- Jubula as a feature in an Eclipse installation. The embedded AUT Agent is started
- on port 60000 by default; this number can be changed in the preferences.
+
</p>
- <img alt="Embedded AUT Agent" src="./new/Indigo/images/EmbeddedAgent.png">
+
</td>
</tr>
-
-<tr>
- <td class="entry_cell">
- AUT Agent now part of the Jubula feature
- </td>
- <td>
- <p>
- There is now no need to use the AUT Agent from the standalone version of Jubula to be
- able to work with Jubula as a feature: The AUT Agent is now included in the
- distribution.
- </p>
- <img>
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node266.html">
- Launch configurations</a> for Swing and RCP AUT's
- </td>
- <td>
- <p>
- When working with the Jubula feature, you can now start your AUT from
- within the IDE as a launch configuration. This is available for Swing
- and RCP AUT's.
- </p>
- <img>
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- Object Mapping Editor: <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node169.html">
- Cleanup unused component names </a>
- </td>
- <td>
- <p>
- In the Object Mapping Editor, there is a new option in the context-sensitive
- menu. Via <b>Cleanup -> unused component names</b> you can start a search for
- any component names that are no longer used in Test Suites for this AUT. Once the
- search is finished, you can delete all of these unused names from the Object
- Mapping Editor. If they are then no longer used in the entire Project, they
- can be deleted from the Component Names Browser.
- </p>
- <img alt="Delete Unused Component Names" src="./new/Indigo/images/DeleteUnusedCompNames.png">
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- HTML Test Result Reports can be expanded again
- </td>
- <td>
- <p>
- Following changes made for the initial contribution, the HTML Test Result Reports
- could not be viewed properly in the previous version. In this release, the nodes
- in the HTML reports can be expanded and collapsed to view the whole test progress.
- </p>
- <img alt="HTML Report" src="./new/Indigo/images/HTMLReport.png">
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node171.html">
- State of component recognition</a> displayed when collecting technical names
- </td>
- <td>
- <p>
- When a component (technical name) is collected from an AUT, it receives a colored
- dot corresponding to the accuracy of the object recognition for this component
- <i>at the time of collecting</i>. A <b>green</b> dot signifies that the component
- could be found with an exact match, and was the only component above the threshold.
- A <b>yellow</b> dot means that the component is an exact match, but that multiple
- other components were also above the threshold. A <b>red</b> dot means that this component
- cannot be relocated in the current state of the application.
- </p>
- <img alt="Object Mapping Colors" src="./new/Indigo/images/ColorDot.png">
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- Migration wizard re-enabled
- </td>
- <td>
- <p>
- When migrating between the Indigo release and SR1, the migration assistant
- will automatically notify you that your database scheme is out-of-date.
- You can then select which Projects to import (these must have been exported
- from the database prior to migrating!).The assistant will drop the tables in the
- database, recreate the necessary tables and import the Projects you specified.
- </p>
- <img alt="Database Migration" src="./new/Indigo/images/Migration.png">
- </td>
-</tr>
-<tr>
-
-<td class="entry_cell">
- Refactor: <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node94.html">
- Replace with Test Case</a>
- </td>
- <td>
- <p>
- In the Test Case Editor and Test Suite Editor, there is a new option to replace one or more
- selected Test Cases with another Test Case from the library.
- A new wizard takes you step-by-step through the replacement process,
- letting you transfer component names and add further information for the new Test Case.
- This feature should help testers who want to restructure their tests
- after creating a reusable module to replace one or more Test Cases.
- </p>
- <img alt="Replace with Test Case" src="./new/Indigo/images/ReplaceTC.png">
- </td>
-</tr>
-
-<tr>
- <td class="entry_cell">
- <a href="http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node83.html">
- Copy ID to clipboard</a> also for Test Suites
- </td>
- <td>
- <p>
- The ability to copy a unique ID to the clipboard to reference a Jubula element
- in external systems has also been implemented for Test Suites.
- You can now copy the ID of a Test Case or a Test Suite to the clipboard,
- and also open an element based on its ID in the clipboard using <b>Shift+F9</b>.
- </p>
- <img alt="Copy ID to Clipboard" src="./new/Indigo/images/CopyIDTS.png">
- </td>
-</tr>
-
-<tr>
- <td class="entry_cell">
- The DBTool is more verbose
- </td>
- <td>
- <p>
- The command line tool to import, export and delete Projects in the
- database, the DBTool, has been updated so that it is more verbose.
- </p>
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- Progress View
- </td>
- <td>
- <p>
- The ITE now uses the progress view to show longer-running activities such as
- test execution, connecting to AUTs etc.
- </p>
- <img>
- </td>
-</tr>
-<tr>
- <td class="entry_cell">
- Edit Parameters Dialog in Central Test Data Editor can be opened via double-click
- </td>
- <td>
- <p>
- In the Central Test Data Editor, it is no longer necessary to open the Edit Parameters
- Dialog via context-menu, as it can now also be opened via double-click on the data set
- you wish to edit.
- </p>
- </td>
-</tr>
-
-<tr>
- <td class="entry_cell">
- Mac keyboards now supported, new mechanism for adding keyboard layout files
- </td>
- <td>
- <p>
- In the AUT configuration dialog for SWT and RCP AUTs, the Keyboard Layout combo box now only offers
- layouts that have been defined for Jubula. German (DE) and English (US) are defined as standard.
- As well as being able to add keyboard layouts for other keyboards,
- you can also define platform-specific keyboard layouts (e.g. for Mac)
- The documentation has been updated to describe the new mechanism for adding keyboard layouts.
- </p>
- </td>
-</tr>
-
-
</table>
-
+-->
<h1>Other information for this release</h1>
<p>
-Read the release notes (available from the <a href="documentation.php">documentation</a> page) for more
+Read the latest release notes (available from the <a href="documentation.php">documentation</a> page) for more
details, including known issues and other important information.
-<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=RESOLVED;bug_status=CLOSED;classification=Technology;product=Jubula;target_milestone=Indigo%20SR1">Closed Bugs for Indigo SR1</a></h2>
+<h2><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED;bug_status=CLOSED;query_format=advanced;list_id=625234;product=Jubula;target_milestone=Indigo%20SR2;classification=Technology">Closed Bugs for Indigo SR2</a></h2>
</div>
</div>
\ No newline at end of file
