new/Indigo/SR1/new_indigosr1.html - gerrit/www.eclipse.org/jubula - Git at Google

 <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="../../Kepler/Main/new_kepler.php">What's New for the Kepler Release?</a></li>
 <li><a href="../../Juno/Main/new_juno.php">What's New for the Juno Release?</a></li>
 <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></li>
 </ul>
 </div>
 <div id="left">
 <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>
	<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="../../Kepler/Main/new_kepler.php">What's New for the Kepler Release?</a></li>
	<li><a href="../../Juno/Main/new_juno.php">What's New for the Juno Release?</a></li>
	<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></li>
	</ul>
	</div>
	<div id="left">
	<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>