Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A Query Test Case consists of a number of Query Variants. If you click on the Variants button, a screen for the Query Variants selection is displayed.



Figure 120. Creation of Query Test Case



Figure 121. Query Test Case variant selection screen

...

The screen for creating new Query Variant is accessible by clicking on the Create new Query Variant button (Shift + F1).


Figure 122. Creating new Query Variant

...

  1. RFC Destination – RFC destination of the Query Variant. When the RFC destination is specified using F4 help, this will display the query name values from the specified destination system. RFC with F4 help is only available if the dialog RFC connection (does not need to be the same as the filled one) is available in the system in the specified RFC destination.
  2. Query name (required) – the technical name of a query. F4 help is available for this field.
  3. Query Variant Description – allows you to add a description for the new Query Variant.
  4. Set query variables  – allows you to specify the filtering values (if any) for a query. For RFC Query Variants there is the possibility to specify the filtering values that are available only if the dialog RFC connection (does not need to be same as filled one) is available in the system to the specified RFC destination. Validate is also installed on the RFC destination system.


Figure 123. Query Filters

5. After image variant – Query/Bookmark Variant ID enables you to compare the outputs for different queries or for the same query on a different system. This can be executed instead of the variant during the creation of an after image.

...

Create New Bookmark Variant 



Figure 124. Create new Bookmark Variant

...

This functionality is available, only if the HeatMap Query Statistics are already installed on the system. After clicking on the button Generate Query Variants from HM (Shift + F6), the screen is displayed where you can define which InfoProvider and Query selection are to be searched for in statistics. 


Figure 125. Specification of filter for queries search


After a filter is specified (optional), you can click on the Continue (Enter) button. The next screen displays the information about queries that are present in HeatMap Statistics and the number of times the query was executed in the system. 
You can generate the Query Variants from these statistics by selecting queries and specifying the number of variants to be created for each of the selected queries. This number only specifies the maximum number of variants that are to be generated. If there are not enough distinct (in terms of used filters) query executions in the statistics, then fewer Query Variants are generated. Variants are then generated after clicking on Continue button (Enter). 


Figure 126. Generation of Query Variants

...

You can also create Query Variants for all of the queries used in specified Web Template. To do this you can click on Create Based on Web Template button (Shift + F8). 


Figure 127. Selection of Web Template

In this screen you can define the Web Template ID and after clicking on Continue button (Enter) the Web Template is searched for all used queries. These queries are presented in a table afterwards (Figure 128) and in this table you can choose the queries to be generated for the Query Variants by using the checkboxes. 



Figure 128. Queries of web template

For each selected query you are presented with the standard Create New Query Variant screen where you can define or change the pre-filled variant values.

...

You can create Query Variants based on a specified Web Template Bookmarks by clicking on Gen. Based on Web Template Bookmark button (Shift + F12). The Screen for Web Template Bookmark ID selection is then displayed (Figure 129). 


Figure 129. Selection of Web Template Bookmarks for Query Variant generation

...

Select multiple variants and create after image variants from them. To access this functionality you need to access the context menu of the selected variants and choose Create After Images as copies. A Dialog is displayed where you can define RFC destination that will be applied to all generated after image variants. All other settings are copied from source variants. 


Figure 130. Create After Image Variants as copies

...

You can compare the chosen settings for variant with its defined after image variant (if there is one). Select the requested variants and choose Compare Settings option from the context menu. 


Figure 131. Compare settings of before and after image variant

...

You can copy settings of variant to its defined after image variant. After the selection of variants is done, you can choose Copy Settings context menu option. A dialog is displayed where you can define which settings should be copied and the source variant for after image variant (if there is any). 


Figure 132. Copy settings of variant to its after image variant

...

You can create copies of Query variants by selecting multiple variants in the selection table and clicking on  Copy Query Variants toolbar button. For each selected variant a new variant is created with exactly the same settings as the source variant. If a copied source variant has a different after image variant specified a copy of this would also be created. The copied after image variant is then assigned to copied source variant as its after image variant. 


Figure 133. Copy Variants

Generate Query Variants from HeatMap Statistics

This functionality is available, only if the HeatMap Query Statistics is already installed on the system. After clicking on the button Generate Query Variants from HM (Shift + F6), the screen displayed is where you can define which InfoProvider and Query selection are to be searched for in statistics. 


Figure 134. Specification of filter for queries search


After a filter is specified (optional) you can click on the Continue (Enter) button. The next screen displays the information about queries that are present in HeatMap Statistics and the number of times the query was executed in the system. 
You can generate the Query Variants from these statistics by selecting queries and specifying the number of variants to be created for each of the selected queries. This number only specifies the maximum number of variants that are to be generated. If there are not enough distinct query executions (in terms of used filters) in the statistics, then fewer Query Variants are generated. Variants are then generated after clicking on Continue button (Enter). 



Figure 135. Generation of Query Variants

...

You can also create Query Variants for all queries used in specified Web Template. To do this you can click on Create Based on Web Template button (Shift + F8). 



Figure 136. Selection of Web Template


In this screen you can define the Web Template ID and after clicking on Continue button (Enter) the Web Template is searched for all the used queries. These queries are presented in a table afterwards (Figure 128) and in this table you can choose the queries to be generated for the Query Variants by using the checkboxes. 



Figure 137. Queries of web template

For each selected query you are presented with the standard Create New Query Variant screen where you can define or change the pre-filled variant values.

...


Afterwards, click on Continue button (Enter); each Web Template Bookmark selected is searched for all used queries. For each query found, a new Query Variant is created. All Query Variants filters are filled with the corresponding filtering values from Web Template Bookmark they were found in. 

...

Copy Query/Bookmark Variants

To create a copy of the existing Query/Bookmark Variants, select the rows with the variants you want to copy and then click on the Copy Query Variants button in toolbar of the table, for . For each selected Query/Bookmark Variant a copy is then created.

Edit Query/Bookmark Variant

You can edit the existing Query/Bookmark variants by double clicking on them in the table, only . Only Variants that are not used in other Test Runs can be edited. If Query/Bookmark Variant is already used in another Test Run it's , its details can be only reviewed but not changed. 
When variant details are displayed, you can check where this variant is used , by pressing the Where Used  button; a table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 

...


By clicking on  Copy Settings to After Image button. you can copy specified settings of this variant into its after image variant if it is specified.

...

You can edit more Query/Bookmark variants at once , by selecting the required variants from the list and clicking on the Mass Edit Variants  button. Dialog for mass edit of variants is displayed. 

...


You can define new values for the before and after image RFC destination. Changing of these values is done after by clicking on Continue (Enter) button. By marking the Edit checkbox, only the values , which that you specify to be changed, will be replaced in selected variants. If Query/Bookmark variant has a different After after Image specified, the After after Image RFC destination will be replaced in that variant otherwise there will not cause won't be any change. Only variants that are not yet used in test runs can be changed by mass edit.

...

  1. Select checkboxes to confirm that you want to apply changes to the selected variants. Click on a Filter Values button to define new values of the InfoObject filters which are used in the queries.
  2. This functionality enables you to define various change rules for before and after image query variants. You need to define required mapping of filter values based on InfoObjects.
     
  3. Confirm the execution of mass editing by clicking the on Continue button.
  4. This step adjusts the filter values of queries based on the specified rules.

...

  • Query filter values are changed based on an InfoObject. When a query contains two variables which are based on the same InfoObject, in the case of mapping, both will be changed.
  • Filter values of queries are changed on a value level. If a Query variant contains for example a range selection (I BT 2006 2007) and mapping is defined for value 2007 => 2008 only the upper boundary of range filter will be changed (I BT 2006 2008). If the same mapping would be used but the previous range filter would change to (I BT 2006 2010) mapping would not be applied.  
  • Mapping values of filters should be defined in a user readable format (the same format as it is used by executing queries in RSRT transaction). The functionality automatically applies correct conversion exits to convert the mapping values to a machine readable format. 
  • Already used query variants in other runs can't be changed using this functionality, as they can't be changed manually. 

...



Selecting Query Variants to be transported


After selecting the desired Query Variants, click on the  Transport Query Variants button, a . A dialog is displaydisplayed, where you can select a request and confirm the transport for the selected Query Variants.

 

Export Query Variants Request Dialog


It is important to note that Query Variants carry information about the query names and filtering values, but not the query structures themselves; therefore these should be imported only to a system where Validate is installed and where the same queries with the same structure exist.

...

To delete an existing Query/Bookmark Variants, select the rows and then clicking click on the delete button in the ALV toolbar. 

Note

Any Query/Bookmark Variants that are still in use in the Backend Testing will be locked; therefore it is necessary to delete the Query Variants from the in the run before deleting them permanently from the Query Variant Editor.

...

You can delete all unused Query variants by clicking on  Cleanup Query Variants button. The First screen displays a preselection pre-selection of filters of the variants where you can restrict which variants should be checked for deletion. After you confirm this screen, a check is performed to find all unused variants. A variant is unused if it is not assigned to any Test Case or Test Run. If a variant is used in another variant as an after image variant and that variant is used in any Test Case or Test Run, it is then evaluated as used on not presented for deletion. 




Query Variant Cleanup PreselectionPre-selection



All variants evaluated as not used are then displayed in the dialog window. When you confirm the selection in this window the variants are deleted from the system.

...