Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMiklos Hartmann2017-05-22 14:58:43 +0000
committerMarvin Mueller2017-06-15 12:12:17 +0000
commitf22d0d9f1563959b16d440a937c68c2e566e89c5 (patch)
tree67bdc6d645f21b322a49e5363277e0baf8aa04b2 /org.eclipse.jubula.documentation
parent3bbd11867bfedd80fbf92c5b10c8f04debc345c6 (diff)
downloadorg.eclipse.jubula.core-f22d0d9f1563959b16d440a937c68c2e566e89c5.tar.gz
org.eclipse.jubula.core-f22d0d9f1563959b16d440a937c68c2e566e89c5.tar.xz
org.eclipse.jubula.core-f22d0d9f1563959b16d440a937c68c2e566e89c5.zip
JUB 1624: Check AUT start from AUT Config Dialog.
Change-Id: Ic670b66cdb291977c782982e65e1ec3a64ec82c7 Signed-off-by: Miklos Hartmann <miklos.hartmann@z-consulting.eu>
Diffstat (limited to 'org.eclipse.jubula.documentation')
-rw-r--r--org.eclipse.jubula.documentation/releasenotes/en/docbook/8.6.0/features.xml14
-rw-r--r--org.eclipse.jubula.documentation/userManual/en/docbook/tasks/startAndConfigureAUTs/sectionConfiguringAUT.xml6
2 files changed, 20 insertions, 0 deletions
diff --git a/org.eclipse.jubula.documentation/releasenotes/en/docbook/8.6.0/features.xml b/org.eclipse.jubula.documentation/releasenotes/en/docbook/8.6.0/features.xml
index 9081fb24b..5b4c8cbe8 100644
--- a/org.eclipse.jubula.documentation/releasenotes/en/docbook/8.6.0/features.xml
+++ b/org.eclipse.jubula.documentation/releasenotes/en/docbook/8.6.0/features.xml
@@ -29,4 +29,18 @@
</para>
</listitem>
</itemizedlist>
+<para>
+ <emphasis role="strong">Try AUT from the AUT Config Dialog</emphasis>
+</para>
+<itemizedlist>
+ <listitem>
+ <para>
+ It is now possible to check if an AUT is startable directly from the AUT Config Dialog.
+ You can use the <literal>Try AUT</literal> button for this. When clicked, the ITE tries to
+ start the AUT (if the ITE is already connected to an AUT Agent, that is used, otherwise
+ the embedded Agent is started). In case of a successful AUT start, the AUT is kept running,
+ otherwise the user is notified of the reasons why starting the AUT failed.
+ </para>
+ </listitem>
+</itemizedlist>
</section>
diff --git a/org.eclipse.jubula.documentation/userManual/en/docbook/tasks/startAndConfigureAUTs/sectionConfiguringAUT.xml b/org.eclipse.jubula.documentation/userManual/en/docbook/tasks/startAndConfigureAUTs/sectionConfiguringAUT.xml
index ef684b2ea..81520fd1f 100644
--- a/org.eclipse.jubula.documentation/userManual/en/docbook/tasks/startAndConfigureAUTs/sectionConfiguringAUT.xml
+++ b/org.eclipse.jubula.documentation/userManual/en/docbook/tasks/startAndConfigureAUTs/sectionConfiguringAUT.xml
@@ -29,6 +29,12 @@
working directories, AUT arguments, Java versions, browser
choices and activation methods.
</para>
+ <para>
+ In the AUT Configuration Dialog, it is possible to try to start the AUT using the entered
+ configuration. This way it is possible to quickly check whether the configuration is correct.
+ Use the <literal>Try AUT</literal> button for this. If the ITE is connected to an AUT Agent,
+ that agent is used to start the AUT, otherwise the embedded Agent is started.
+ </para>
<para role="tip">
If you want to start your Java AUT yourself, and have the ITE connect to it, then use the <emphasis>autrun</emphasis> command to start the AUT (<xref linkend="starting-java-with-the-command"/>). In this case, you do not need to create an AUT configuration.
</para>

Back to the top