We've had some inquires recently about how you use eValid's random input test data capability to drive inputs during a LoadTest run.
This turns out to be simple enough. You use the eV.Generate random number generation to create the random strings that you need for input, and you can prevent two (or more) eValid instances from creating a conflict as the random number process runs with a Lock/Unlock command.
There's a complete explanation of this process in the Random Email, Context Confirmation, Loading Example, which focuses on creating email accounts.
This example also uses a little bit of DOM manipulation to make sure that a submitted random email account "verifies" correctly by retyping it as a confirmation. (You need this extra step because a second run of random email account name generation will produce a different results.)