Most of my customers have the requirement to test a highly integrated bit of functionality called "Grouping Pegging and Distribution" (GPD).
GPD is a background process that interacts with a very large set of tables, and depending on the contents of the tables, may access/interact with addititional sets of tables.
The challenge that my customers face in using TDMS is that they can not identify the full subset of tables required to migrate into a test system.
The question I have is - do we have a way to "scan" a program and all of it's calls, to automatically generate a TDMS project??
Having something that could essentially trace the program logic, and automatically build the required set of tables for a test would be very valuable!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.