Test Generation Desktop
The Test Generators will overwrite existing tests. There is no warning.
Some basic tests can be generated automatically under Generator.
It is recommended to create a Test Generation Configuration before you start one of the Test Generators provided by MyITest4U.
Under Config / Test Configuration you can build your Test Generation Configurations. The main part of the Test Generation are the GUI elements which should not be used in Test Generation like "Logout", "Close", "Exit" etc. The GUI elements which should not be included in test generation can be set for every window or ControlType. Is a window excluded from test generation all GUI elements on this window are excluded from test generation. The excluded windows and their GUI elements will not show up any more under the Test Generation menu.
Any change made to the Test Generation Configuration is saved immediately (excludefromtestgen a GUI element property is changed from false to true an the MyITest4U database). The current Test Generation Configuration can be viewed and saved to be reused later on using the Test Configuration Summary dialog (Config / Test Generation / Summary). As changes to the Test Generation Configuration are saved on GUI element level on the database, it is not possible to show the name of the currently active Test Generation Configuration. To save a change to a loaded Test Generation Configuration the Test Generation Configuration needs to be Saved / Updated using the Test Configuration Summary dialog.
Set Default Exclude will set the following ControlTypes to be excluded from test generation:
- DataGrid
- Header
- MenuBar
- Pane
- ProgressBar
- ScrollBar
- Separator
- StatusBar
- Tab
- Table
- Text
- Thumb
- TitleBar
- ToolBar
- Tree
Set Local Excludes form Global Excludes will set all GUI elements containing the Global Exclude to be excluded from Test Generation.
Under Config / Local / Test Generation GUI Elements / Configure Edit Fields can a default input value be set for all Text fields.
Config / Summary shows a summary of all your Configuration Settings.
The current configuration is stored. The configuration used to generate certain tests is not stored together with the generated tests.
The following tests can be generated:
- Generate Window Template
- Visit do Default Action
- Visit set Default Inputs do Default Action
The default action for each ControlType is given below.
| ControlType | Default Action |
|---|---|
| Button | Click |
| CheckBox | Select |
| ComboBox | Select |
| Custom | Click |
| DataGrid | Click |
| DataItem | Click |
| Document | SetText |
| Edit | SetText |
| Group | Click |
| Header | Click |
| HeaderItem | Click |
| Hyperlink | Click |
| Image | Click |
| Key | Press |
| List | Click |
| ListItem | Select |
| Menu | Click |
| MenuBar | Click |
| MenuItem | Click |
| NoGuiElement | FindAppWindow |
| Pane | Click |
| ProgressBar | Click |
| RadioButton | Select |
| ScrollBar | Click |
| Separator | Click |
| Sleep | Sleep |
| Slider | SliderSetValue |
| SpecialKey | Press |
| Spinner | Click |
| SplitButton | Click |
| StatusBar | Click |
| Tab | Click |
| Table | Click |
| TabItem | Select |
| Text | CheckText |
| Thumb | Click |
| TitleBar | Click |
| ToolBar | Click |
| ToolTip | CheckToolTip |
| Tree | Click |
| TreeItem | Click |
| Window | Click |
Generate Window Template
This test generator will create a test for each Window of your application. The generator uses the information stored in the MyITest4U data base in the following way:
- A search for all Windows is done.
- A search for all GUI elements belonging to a Window is done.
- The GUI elements having Button as ControlType are moved to the back of GUI element list.
- The test steps are build using the Default Action for each ControlType of the GUI element.
Visit do Default Action
This Test Generator will create a test visiting all GUI elements of the given ControlType and doing the Default Action.
A use case for this Test Generator could be to create a test clicking all menus of the application.
Visit set Default Inputs do Default Action
This Test Generator will create tests in the following way:
First you have to select the ControlTypes which should get a value like Edit.
In the next step the ControlTypes which will trigger the action to be done can be selected like Buttons.
An example of this kind of test generation is:
The AUT has a form with some entry fields and two buttons like OK and Cancel.
The generated test will create all test steps for filling in the entry fields.
After these steps OK or Cancel would be clicked.
The following applies for using this Test Generator:
- All windows containing the second ControlType will be visited independent if the first ControlType is present or not (use Window to Exclude to exclude windows which do not contain the first ControlType).
- No "plausibility" checks are done e.g. it is possible to select Button in both steps.
- Very large tests might be generated if you select to many ControlTypes in either step of the Test Generation.
- It might be better to use the Generate Window Template test generator and use the Additional Parameter Ignore to generate similar tests.