Difference between revisions of "GXtest Generator - Test depth"

From GXtest Wiki
Jump to: navigation, search
(Options)
Line 27: Line 27:
 
The rules that are currently analized/supported are:
 
The rules that are currently analized/supported are:
 
* error() - when the error depends on a numeric attribute comparison
 
* error() - when the error depends on a numeric attribute comparison
 +
* error() - when the error fires if an attribute value is empty
 +
* error() - when the error fires if the lenght of a string is greater or lower than a numeric value
  
 
=== Valid and Invalid ===
 
=== Valid and Invalid ===
 
Not implemented yet in current builds of GXtest.
 
Not implemented yet in current builds of GXtest.

Revision as of 12:49, 14 April 2015

Spanish.gif
English.gif
Japan.gif

The Test depth option specifies the data complexity that the generated Test Cases will have. The number of rows that the generated datapools will have depends on this configuration.

Contents

Options

It has 4 options:

  • Minimum
  • Basic
  • Basic with rules
  • Valid and Invalid


Minimum

It generates only one value for each editable field of the entity analized. The value may be ramdomly generated, or could be taken from a Dictionary or the application database.

Basic

It generates a set of valid values for each field, based on the border values of those fields. For example, for a Numeric(4) field, it could generate the following values: 183, 0, 1, 9999

Basic with rules

Same as Basic, but also includes border values based on the GeneXus rules of the analized objects.

The rules that are currently analized/supported are:

  • error() - when the error depends on a numeric attribute comparison
  • error() - when the error fires if an attribute value is empty
  • error() - when the error fires if the lenght of a string is greater or lower than a numeric value

Valid and Invalid

Not implemented yet in current builds of GXtest.