topic Re: eCATT: Dynamic <target system> for pattern REF possible? in Application Development and Automation Discussions

eCATT: Dynamic for pattern REF possible?

Former Member — Fri, 07 Dec 2007 14:42:05 GMT

Hello

I am using eCATT on a Solution Manager (NetWeaver 700). I have to run the test scripts on several different SAP systems.

Therefore, I would like to know whether it is possible to set the target system within the pattern REF (executes another eCATT test script, either on local or remote system) dynamically?

Definite proof that this is not possible is also welcome.

I am aware that I can replace the REF pattern by a corresponding ABAP...ENDABAP coding, e.g.:

FUN ( BAPI_USER_EXISTENCE_CHECK , BAPI_USER_EXISTENCE_CHECK_1, <target_system> ).

Replace by:

ld_rfcdest = id_rfcdest.
ABAP.
  CLEAR: ls_return.

  CALL FUNCTION 'BAPI_USER_EXISTENCE_CHECK'
    DESTINATION ld_rfcdest
    EXPORTING
      username = id_username
    IMPORTING
      return      = ls_return.
" NOTE: Not necessary to handle RFC exceptions -> done by eCATT framework
ENDABAP.

" evaluate ls_return...

However, I would prefer - if possible - to use the REF pattern.

Regards,

Uwe

Re: eCATT: Dynamic for pattern REF possible?

uwe_schieferstein — Sat, 15 Dec 2007 23:47:18 GMT

Hello

In case you may need this functionality here is (one possible) solution.

The testscript ZUS_SDN_ECATT_DYNAMIC_TARGET calls testscript ZUS_SDN_LOGICAL_SYSTEM_GET dynamically on different target systems.

Testscript ZUS_SDN_ECATT_DYNAMIC_TARGET:


*ECSC	Test Script
*ECTD	Test Data Container
*ECSD	System Data Container
*ECTC	Test Configuration

ls_execute = is_execute.
ABAP.
  APPEND ls_execute TO lt_execute.
ENDABAP.
et_execute = lt_execute.

FUN ( ECATT_EXECUTE , ECATT_EXECUTE_1 ).
CHEVAR( &EXCEPTION = ' ' ).
EXIT( &EXCEPTION <> ' ' ).

**FUN ( ECATT_LOG_DISPLAY , ECATT_LOG_DISPLAY_1 ).

The funny part of this script is the FUN pattern where I call function module ECATT_EXECUTE which is used to execute testscripts (or test configurations). As IMPORTING parameter we have a structure START_PROFIL where we can set the SYSTEMDATA (container) and the TARGETSYSTEM.

Hopefully I will find the time to explain this testscript and its possible use and implications in more detail in a blog.

Regards,

Uwe