Author:halw

Date:2009-03-12T03:01:12.000000Z


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

documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki

@@ -25,7 +25,11 @@ If you've been through the discussion of the creation of [[Create a manual test|
 
 In the first pane, choose the radio button labeled '''Synthesized test using AutoTest'''. Then click '''Next'''. 
 
-The second pane is the now familiar pane that asks you to provide a class name for the new test class and designate a cluster for it. In the case of synthesized tests, the class name you enter is actually a prefix, that will have a sequential number appended to it. This means that for the <code>BANK_ACCOUNT</code> example, if we might choose a test class name like <code>TEST_BANK_ACCOUNT_SYNTHESIZED</code>, the first test class with that prefix would be named <code>TEST_BANK_ACCOUNT_SYNTHESIZED_001</code>.
+The second pane is the now familiar pane that asks you to provide a class name for the new test class and designate a cluster for it. In the case of synthesized tests, the class name you enter is actually a prefix, that will have a sequential number appended to it. This means that for the <code>BANK_ACCOUNT</code> example, if we might choose a test class name like <code>TEST_BANK_ACCOUNT_SYNTHESIZED</code>, the first test class with that prefix would be named <code>TEST_BANK_ACCOUNT_SYNTHESIZED_001</code>:
+
+
+[[Image:New test wizard screen 02S 01]]
+
 
 In the third pane, you are asked to configure certain options for the generation of synthesized tests: 
 

documentation/current/eiffelstudio/eiffelstudio-reference/autotest/autotest-interface.wiki

@@ -8,7 +8,7 @@
 [[Image:Testing Framework interface annotated 01]]
 
 
-The interface consists of four primary components: 
+The Eiffel Testing Framework interface consists of four primary components: 
 # The toolbar
 # The view filtering controls 
 # The tests view
@@ -67,7 +67,7 @@ After execution or debugging, the tests executed and their status are shown in t
 [[Image:Testing Framework interface results - Execution]]
 
 
-Double clicking a test in the '''Tests''' pane will switch the '''Status and results''' pane to the '''Results''' tab. This tab shows a history or the executions and results of that particular test. 
+Double clicking a test in the '''Tests''' pane will switch the '''Status and results''' pane to the '''Results''' tab. This tab shows an expandable history of the executions and results of that particular test. 
 
 
 [[Image:Testing Framework interface results - Results]]

documentation/current/eiffelstudio/eiffelstudio-reference/autotest/eiffel-test-wizard.wiki

@@ -37,11 +37,71 @@ In this pane you provide a name and cluster for the test class that will be crea
 
 ===The "Test routine" pane===
 
-This pane gives you the ability to name the test, and to associate it with certain [[Create a manual test#About tags|tags]].
+This pane gives you the ability to name the test, and to associate it with certain [[Create a manual test#About Tags|tags]].
 
 
 [[Image: New test wizard screen 03M 01]]
 
 
+For tags, there are two entry boxes with '''Add''' buttons to their right. You can use the top entry box to create entries for a tag system that you have developed. 
+
+On the bottom box, use the drop-down arrow to choose a predefined tag, such as associating the test with a target class and routine.
+
+
+==The extracted test thread==
+
+
+The '''Extract tests from running application''' radio button is only sensitive if the system is currently running. 
+
+Creating extracted tests will involve using the following wizard panes. For a guided tour of this process, see [[Using extracted tests]].
+
+
+===The "New test class" pane===
+
+For extracted tests, the second pane to appear is the '''New test class''' pane. It is completed just as for manual tests.
+
+
+===The "Extract application state" pane===
+
+
+[[Image:New test wizard screen 03E 01]]
+
+
+This pane provides a depiction of the current call stack. Choose the routine or routines for which you want extracted tests to be created.
+
+
+==The synthesized test thread==
+
+
+Creating synthesized tests will involve using the following wizard panes. For a guided tour of this process, see [[Using synthesized tests]].
+
+
+===The "New test class" pane===
+
+
+[[Image:New test wizard screen 02S 01]]
+
+
+This pane appears slightly different for synthesized tests versus manual or extracted tests. The class name is actually a prefix upon which a numeric index will be appended. The index is depicted to the right of the entry box. 
+
+
+===The "Generate tests through AutoTest" pane===
+
+
+[[Image:New test wizard screen 03S 01]]
+
+
+On this pane enter the information needed to produce synthesized tests. Use the '''Class or type name''' entry box in the lower left, along with the <code>+</code> and <code>-</code> buttons, to declare a list of one or more classes as target classes for synthesized tests. 
+
+Other information necessary for creating synthesized tests is:
+
+*'''Duration (minutes)''' -- How long the Eiffel Testing Framework will execute random invocations of the routines in the classes to be tested.
+*'''Routine timeout (seconds)''' -- How long the Framework will wait for completion of any invocation.
+*'''Random number generation seed''' -- The seed used for random number generator used during the process. A value of zero instructs the Framework to use a seed derived from the system clock.
+*'''Use slicing for minimization''' -- Designate '''slicing''' as the approach for minimizing the size of synthesized tests.
+*'''Use ddmin for minimization''' -- Designate '''ddmin''' as the approach for minimizing the size of synthesized tests.
+*'''Create html output''' -- Output history and statistics from the synthesizing process in html format.
+
+
 
 

documentation/current/eiffelstudio/eiffelstudio-reference/autotest/index.wiki

@@ -6,7 +6,9 @@
 
 ==Introduction==
 
-The Eiffel Testing Framework is a facility within EiffelStudio that helps developers create, manage, and execute software tests. These pages are intended to describe the Eiffel Testing Framework interface and capabilities. In addition to this material, you will find a tutorial entitled [[Using the Eiffel Testing Framework]] in [[EiffelStudio: A Guided Tour]]. The tutorial includes a simple example that you can use to work through the Testing Frameworks different facilities. It also contains definitions for terminology used in the tutorial and in this reference. Specifically:
+The Eiffel Testing Framework is a facility within EiffelStudio that helps developers create, manage, and execute software tests. 
+
+This documentation is intended to describe the Eiffel Testing Framework interface and capabilities. In addition to this material, you will find a tutorial entitled [[Using the Eiffel Testing Framework]] in [[EiffelStudio: A Guided Tour]]. The tutorial employs a simple example that is used to work step-by-step through the Testing Framework's different facilities. The tutorial also explains testing basics and recommendations for using the Eiffel Testing Framework. Lastly, the tutorial contains definitions for terminology used in both the tutorial and in these reference pages. It is recommended that you become familiar with these definitions, specifically:
 
 #[[Testing: Background and basics#Test classes and tests|Test classes and tests]]
 #[[Testing: Background and basics#Types of tests|The types of test supported by the Eiffel Testing Framework]]
@@ -14,6 +16,7 @@ The Eiffel Testing Framework is a facility within EiffelStudio that helps develo
 #[[Execute tests#About test results|Test results]]
 
 
+
 ==Components==
 
 When you use the Eiffel Testing Framework, you control things by using two components: '''[[The Eiffel Testing Framework Interface]]''' and '''[[The New Eiffel Test Wizard]]'''. The interface is used to access, manage, execute, and monitor tests. The New Eiffel test wizard is used to help you create new tests.