![]() Quantity – RandomNumber ( 1 5 0 ) // random number between 1 and 5.Type – RandomValueFromValueList ( “Invoice Type” ).For example, if you wanted to do this for creating invoice records, you could set it up like this: The demo file tracks contacts data, but these custom functions can be used for any type of data. Type Of Data Supported (Not Just Contacts) Setting up the script takes a few minutes, but it’s well worth it, because it then becomes quick and easy to create realistic test data. I place a button to call the script on the layouts where I need it for testing, and I use the FileMaker 13 “Hide object when” feature to hide the button when the user is not a full access user. The script fills in all of the fields using the custom functions. Now I’ve gotten in the habit of creating a script for each entity (table) that I have to create test data for. There’s also a custom function in there that selects a random value from a value list that you specify. ![]() Address (Street, City, Zip, State, Country).To address this problem, I created a set of custom functions to create data for the most typical types of fields: The net effect of this manual entry is it discourages effective testing. If there’s data validation in place, then I’m in real trouble. Pretty soon, I’m just typing in “xxx” or “asdf”. If I also need to enter in address data, I’m hopeless. If the fields requiring a value include a name field, I’m good to go for about 5-6 records, until I exhaust the ‘first name’ supply that I seem to keep handy in my brain. When testing the functionality of a solution, software developers frequently have to create test records, which requires them to enter in test data. Manual Entry of Test Data Discourages Testing
0 Comments
Leave a Reply. |