on 06-27-2013 2:56 PM
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!!
Hello Jim,
TDMS already has program that scans the entire respository to see the tables to be transferred. If there are additional tables that are not maintained in TDMS customizing then these "additional" tables are also marked for full transfer. Subsequently you have a UI activuty where you can decide which tables should be transferred in full or not to be transferred at all.
Hope this helps.
Best Regards
Malthi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jim,
I can only think of using table D010TAB (Table for Use Report<->Tables) but other than that use ST05 or try ST12 to trace the program and see what tables are used
Best Regards
Marius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.