Simulating Controls
When you record transactions that use Controls in a test case, the Control data flows between application server and frontend are recorded.
The Controls are simulated when the test case runs. The Controls are deactivated and the recorded data flows are read in. You can then test the reaction of the transaction to Control events (e.g. double-click on a node in an SAP Tree Control).
The recorded Control data must be the same as the test data. A data change could invalidate the test (e.g. the node for a double-click no longer exists).
The Control functions are only tested when recorded, not at test runtime.
Manual modification of the test case to reflect transaction or data changes is often problematic. You should