This eValid data synthesis playback mode allows a single parameterized script to play back many instances with parametric values selected from a simple user-assigned value table. The eValid data synthesis option is different from the eVgenerate facility in these ways:
The Test Data Synthesis table has a very simple format.
Script Modification Required
Two forms of script modification are needed to implement the eValid Test Data Synthesis Option:
...$PARA1=valueA... ...$PARA2=valueA... ...$PARA1=valueB... ...$PARA2=valueB... ...$PARA1=valueC... ...$PARA2=valueC...
Here is an example Test Data Synthesis table that specifies values for use in running a test of a site login sequence.
$ACCOUNT=firstuser $PASSWORD=gobbler $ACCOUNT=seconduser $PASSWORD=hatchet $ACCOUNT=WonderBread $PASSWORD=goofy $ACCOUNT=george $PASSWORD=superprogrammer
Here is a fragment of an eValid script that shows use of the parameters that are supplied by the Test Data Synthesis table.
# Regular eValid Playback Script ... DataSynthesisFile "example.txt" ... GoToLink ...URL...?Account=$ACCOUNT & Password=$PASSWORD... ...
The Test Data Synthesis table has four lines, so when you invoke eValid's Data Synthesis Playback Mode using the Playback Mode > Control Playback > Run Synthesized you will automatically run the specified script four times, one each for the combinations of values in the table.
The logfiles generated are the SAME as if you used the Run Multiple playback option: Each sequential playback is separated in the logfiles as if there were separate tests being run.
Note that in case the Data Synthesis File is not found, this will be noted as an error message in the event log. Without a Data Synthesis File defined, playback of the script with $PARAMETERS will likely fail.
Special characters can be substituted for these characters:
|You Type This...||To Get This Character...|
|%09||\t (TAB character)|
|%20||" " (Space character)|
|%22||" (Double quote character)|
|%24||$ (Dollar sign)|
|%25||% (Percent sign)|
|%3D||= (Equal sign)|
|%0D||\r\n (New line)|
Constraints and Limitations
Note: In some cases a double quotes (") must be used to enclose the parameters that refer to the fieldnames to be substituted in the script. By doing so, a blank (null) entry ($FIELDNAME= ) in the data file will be substituted, not ignored.