Author:halw

Date:2009-11-06T22:44:34.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@352 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/eiffelstudio/_images/External_commands_tools_menu_0.png.data

@@ -0,0 +1,3 @@
+title=External commands tools menu
+author=halw
+path=content/external-commands-tools-menu

documentation/current/eiffelstudio/_images/Outputs_tool_General_pane.png.data

@@ -0,0 +1,3 @@
+title=Outputs tool General pane
+author=halw
+path=content/outputs-tool-general-pane

documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/eiffelstudio-6-release-notes/release-notes-eiffelstudio-65.wiki

@@ -16,6 +16,13 @@
 * Click [[Major changes between ISE Eiffel 6.4 and ISE Eiffel 6.5|here]]  for the compiler release notes.
 
 == AutoTest==
+* <strong>Library: <eiffel>EQA_TES_SET.on_prepare</eiffel> is now called during <eiffel>default_create</eiffel>, making it simpler to write void-safe tests.</strong>
+* Library: Added the possibility to wrap the actual test routine call.
+* AutoTest traverses all writeable clusters in the project for possible test classes, making &lt;tests&gt;-clusters obsolete. The traversal happens in the background allowing the user to continue to work on the project.
+* Tags can be used to control the test execution flow. Tagging a test with "execution/isolated" makes the test execute in a separate evaluator process, meaning the evaluator is restarted before and after executing the corresponding test (useful for tests relying on the initial access to a once routine or tests which possibly leave the memory corrupted).<br />Also any tag of the form "execution/serial[/*]" groups the tests to ensure that they are not executed in parallel (useful when a group of tests share a resource which has to be accessed sequentially).
+* Any results are stored between EiffelStudio sessions.
+* Improved the management of existing tests by merging the "View" and "Filter" box into one input field.
+* Improved bottom part of AutoTest tool by only having two tabs displaying test execution and test creation results.
 
 ==Debugger==
 * Click [[Release notes for EiffelStudio 6.5 related to the debugger|here]]  for the EiffelStudio debugger release notes.

documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/general-output-pane.wiki

@@ -3,5 +3,5 @@
 [[Property:uuid|549e254e-3653-db7a-8874-c71b05c9295a]]
 The General output pane contains information about the current EiffelStudio project.
 
-
+[[Image:Outputs tool General pane]]
 

documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/external-commands-editor-dialog.wiki

@@ -3,6 +3,9 @@
 [[Property:uuid|9f8de904-3d17-7ce2-1df8-f4824fab5ae3]]
 From EiffelStudio, you can define up to 10 external commands. Those commands will have their output redirected in the output pane of the context tool. You can execute them through the Tools menu. A typical usage is to use those external commands to integrate with your source control management solution (e.g. CVS, Visual SourceSafe,...)
 
+
+==Defining external commands==
+
 To define your own command, select "External commands..." in the Tools menu. Then the following dialog will appear:
 
 
@@ -20,7 +23,7 @@ To add your first command, simply click on the "Add..." button and the following
 [[Image:external-commands-dialog-editor]]  
 
 
-In this dialog you can give a name to the command, this name will be displayed in the Tools menu. The index is the position among the external commands of the command in the Tools menu. The command line is the command you want to execute. In order to execute correctly, the application you will execute needs to be in your PATH environment variable or if it is not you must provide an absolute path to the external command. And you can specify the working directory for that command.
+In this dialog you can give a name to the command, this name will be displayed in the Tools menu. The index (0 thru 9) is the position among the external commands of the command in the Tools menu. The command line is the command you want to execute. In order to execute correctly, the application you will execute needs to be in your PATH environment variable or if it is not you must provide an absolute path to the external command. And you can specify the working directory for that command.
 
 In addition to the external command name, you can pass as many options as you want plus the following placeholders that will be translated before calling the external command:
 * $class_name: this will be replaced by the name in lower case of the targeted class in editor
@@ -32,5 +35,25 @@ In addition to the external command name, you can pass as many options as you wa
 * $f_code: this will be replaced by the F_code directory of current system, if defined
 
 
+==Executing external commands==
+
+When you look at the EiffelStudio '''Tools''' menu, you will see that the external commands that you have added have also been added to the bottom of the menu. In the figure below, you see the command we added at index 4:
+
+
+[[Image:External commands tools menu]]
+
+
+To execute that command, you can select it from the '''Tools''' menu, or you can use the keyboard shortcut provided. In this case the keyboard shortcut is the default value of '''Alt+4'''. 
+
+The shortcuts for the command indexes can be changed in the EiffelStudio preferences by following the preference path:
+<code>
+        shortcuts -> external_commands
+</code>
+
+External commands execute in the context of the [[Console tool]]. The console tool should appear automatically, but you can make it visible by following the menu path:
+<code lang="text">
+        View -> Tools -> Console
+</code> 
+Then you can dock the console tool, if you would like to have it constantly visible.