Test Data Generator
Is the Test Data Generator a scriptable object at all; or, failing that, is there any way to persist a definition of data to generate? I was about half-way through a very large test data definitio...
Forum Discussion
Hi Irene (if this is the Irene that I worked with years ago at AQA, doubly-"hi");
For other applications of scriptability, yes, I'd can see a number of possible uses. Most notable for me would to be able to dynamically create test cases and data for large numbers of smoke tests.
To be more specific, my current position is as Architect of a conversion framework for modernization of mainframe applications; moving them into the .NET world. We have a conversion tool that does a sort of broad-sweep of conversion and before we move on to less-autometd steps in the conversion process, I'd like to perform a set of smoke tests for each converted project. Part of this would be checking to see whether the converted applications can open and interact with data that has also undergone conversion from the mainframe side.
Most of the time, we either don't have test data, or the test data we have from our client is unusable. Here is where I'd want to be able to automate the process of generating test data in the proper definition, so that my test scripts can try opening a few records.
Since our conversion process targets hundreds of projects at a time, this will only be managable via automation.
Thus, in a nightly conversion/smoke test run, I'd want to be able to convert hundreds of mainframe apps to .net, to dynamically create test data (either in ABS or in TestComplete) for each converted project and to run some simple data smoke tests, viewing the results in the morning to determine whether to proceed with our conversion process...
Please let me know if you need more information...
For other applications of scriptability, yes, I'd can see a number of possible uses. Most notable for me would to be able to dynamically create test cases and data for large numbers of smoke tests.
To be more specific, my current position is as Architect of a conversion framework for modernization of mainframe applications; moving them into the .NET world. We have a conversion tool that does a sort of broad-sweep of conversion and before we move on to less-autometd steps in the conversion process, I'd like to perform a set of smoke tests for each converted project. Part of this would be checking to see whether the converted applications can open and interact with data that has also undergone conversion from the mainframe side.
Most of the time, we either don't have test data, or the test data we have from our client is unusable. Here is where I'd want to be able to automate the process of generating test data in the proper definition, so that my test scripts can try opening a few records.
Since our conversion process targets hundreds of projects at a time, this will only be managable via automation.
Thus, in a nightly conversion/smoke test run, I'd want to be able to convert hundreds of mainframe apps to .net, to dynamically create test data (either in ABS or in TestComplete) for each converted project and to run some simple data smoke tests, viewing the results in the morning to determine whether to proceed with our conversion process...
Please let me know if you need more information...