06-30-2010 11:02 AM
TEST_ECATT: RFC-connection to Q-System
Script is stored in D-System, and first executed local, then in Q-System with the TEST_ECATT-connection.
I have a testscript which looks like this:
V_USER = P_I_USER.
FUN ( RFC_MODIFY_R3_DESTINATION , RFC_MODIFY_R3_DESTINATION_1 ).
REF ( Z_TS_HCZ_VA01_1 , Z_TS_HCZ_VA01_1 , TEST_ECATT ).
In RFC_MODIFY_R3_DESTINATION_1 I have parameterized USER with V_USER. When I run this script and check "Close RFC-connection" in start options, then it works.
Next I made a test configuration for this script with two users for P_I_USER. The protocol says that the update for TEST_ECATT worked.
But it seems that the RFC-connection is open from the first variant to the second and the user doesn't change.
I tried RFC_CONNECTION_CLOSE with the importparameter "TEST_ECATT" at the end of the script, but it says, that the connection isn't open.
I also checked "Close RFC connection" in the test configuration start options, but this doesn't work.
Any ideas?
07-07-2010 10:18 PM
Hi!
I am not 100% sure, but I think, that eCATT is using a temporary copy of the specified RFC connection during test execution. So if you change the user in the original RFC connection from system data container (targetsystem), it will not affect currently running executions.
Hope this helps - best regards,
Christoph