Hello Marsha and Alex, thank you for the replies and suggestions, I will check into these. And yes, they would need to be different each time I run the test as the app does indeed behave differently for duplicate addresses. So what I'll need is to be able to generate an address, that has not been used by my script, for a given state and city upon request. Each time the tests are executed. Has to be valid address, but different each time I run and I need to be able to either generate a list that I can farm the data from or create/poll on the fly, and use for a test, then the next time I run, again would need another valid address for that State and City. I'll need to specify State and City (as the test will only deal with a few certain states and cities), and will need to pull : State, City, Street, and Zip.
Thanks again.
Ron F.
------------
Hi,
To add to Marsha:
I still think that the possible solution depends on the details that we don't know.
For example, if your tests are executed using clean target database every time and the amount of tests that require addresses is not big, then you may create a list with dozen or two of real addresses taken from, say, Google maps and reuse this list for your testing.
Alternatively, if your tests are executed against the same database and validation service requires real existing addresses, than I would consider ReadyAPI Virtualization. It will require some efforts to be set up, but after that can be used instead of real validation service and you will be able to feed it with any combination of state, city, street and zip (generated using means provided by TestComplete) and imitate passed or failed validation.
Probably other options are possible depending on those additional details about your tested application.
