Вы находитесь на странице: 1из 32

2007

7/9/2007
SAP eCATT Tutorial
Table of Contents
Introduction...................................................................3
Part 1 - Creating a Test Script..........................................4
Part 2 - Executing a Test Script........................................6
Part 3 - Chaining a Series o Transactions.......................10
Part 4 - !oops" Conditions" and In#ine $%$P...................14
Part & - 'sing S(ste) *ata...........................................1+
Part 6 - Test *ata Containers........................................23
Part 7 - 'sing Test Con,gurations and -ariants.............2&
Part . - -ersions..........................................................2.
Introduction
This tutorial assumes no prior knowledge of eCATT or CATT. You work through an series of exercises that
build on the knowledge developed in the preceding ones.
Test scripts usually make R/ !ystem database changes" do this tutorial in a
training system.
Learning Targets
You learn to#
!tart eCATT and record transactions
$xecute test scripts
%arameteri&e and reference test scripts
'se inline A(A%) loops) and conditional processing
$xecute test scripts in remote systems
Create test data containers and variants
'se test configurations
'se versioning
Prerequisites
You have the appropriate authori&ations to use eCATT) and for the transactions *+,- and *+,..
The system contains the transactions *+,- and *+,.) and table /*A-.
Part 1 - Creating a Test Script
Use
You learn to start eCATT) create a test script) and record a transaction.
Prerequisites
You are logged on to an !A% !ystem and are in the SAP Easy Access screen.
Procedure
1. !tart transaction !$CATT.
You are now in Extended Computer Aided Test Tool: Initial Screen.
2. !elect Test Script.
3. $nter a name for the script. *or this tutorial) choose XYZ_FK01 0where 1Y2 are your initials3.
4. 4n the Version field) enter 1.
5. 5ake sure the External Tool field is empty.
6. Choose .
7. !creen Create Test Script: XYZ1_!"1#1$ appears.
8. Choose the Attri%utes ta%&
9. $nter a title) for example Transaction FK01.
10. $nter a component) for example BC-TWB-TST-ECA.
11. Choose the Editor tab.
12. 4n the application toolbar) choose Pattern.
The Insert statement dialog box appears.
13. 4n the Command field) choose TC' #(ecord$.
14. 4n the Transaction field) enter the transaction code FK01 and choose .
4n the Inter)ace field) a system6generated name) FK01_1) appears.
15. Accept the system6generated name by choosing .
The transaction starts.
The transaction
The transaction that you will record is Create Vendor 0transaction code *+,-3. You do not need to
be familiar with this transaction. 4t simply creates a record of the name) address) and a few other
details of a customer that you invent. The re7uired fields 0with suggested values3) and the
screens they are on) are listed here#
To record the transaction !"1) you need to leave Vendor field empty. This is because the field
will be filled by an automatically generated number at the end of the transaction.
Screen Field Value
Create Vendor: Initial Screen Vendor 5ake sure this field is empty.
Company code 0001
Account *roup KRED
Create Vendor: Address +ame A N Othr
Searc, terms OT!ER
City !i"#$r%
Country DE
Create Vendor: Accountin*
in)ormation Accountin*
(econ& account 1&0000
Cas, m*mnt& *roup E&
16. 8ork through the transaction) entering the re7uired data in the appropriate fields. !ome of the
screens do not re7uire any input. After you complete each screen) choose .
The -ast data screen reac,ed dialog box appears after the last screen.
17. Choose Yes to save the data.
The system returns you to the script editor with the (ecordin* Ended dialog box.
18. Choose Yes to transfer the data to eCATT.
TCD ' FK01( FK01_1 ). appears in the command editor.
19. Choose . and in the following dialog box choose -ocal o%/ect.
Result
You have created a test script and recorded a transaction.
The transaction has written a new record in the table /*A-. You can view this table using the 9ata
(rowser 0transaction !$-:3.
Part - !"ecuting a Test Script
Use
You learn to execute an existing test script and examine the log.
You will execute the script in background processing mode) then in foreground processing mode) and
finally in error mode. These modes allow different levels of visibility and interaction with the script while it
is executing.
Prerequisites
You are logged on to a !A% !ystem and are in Extended Computer Aided Test Tool: Initial Screen&
You have completed the part - of this tutorial.
Procedure
1& !elect Test Script) and enter the name of the script that you created in part - of this tutorial.
0& Choose .
The C,an*e Test script: XYZ_!"1 #1$ screen appears.
1& Choose the Editor tab.
2& 4n the parameter list) choose to display the command interface.
3& !elect the command interface *+,-;-) and choose to display it in the structure editor.
4& 4n the structure editor) expand the tree and select the first screen.
5& Choose ) to go to the screen simulation.
6& 4n the Vendor field) enter two apostrophes 0 ** 3.
This forces eCATT to clear the field each time the script is executed.
7& Choose .
1"& 4n the structure editor) look in the tree for the field <R*,.+6/4*=R< of the first screen. 9ouble6click
the field to display it in the grid on the right6hand side of the structure editor.
You should see that the VA-I+ field contains four apostrophes. *ixed values in the structure
editor are designated by apostrophes. 4nstead of using the screen simulation) you could have
entered the apostrophes directly in the structure editor.
#ac$ground Processing
11& 4n the structure editor) double6click the top node) and enter *N* for the value of the mode.
You must use apostrophes because it is a fixed value.

10& Choose Enter.
11& Choose .
12& Choose .
The Start 8ptions dialog box appears.
13& 4n the Error ,andlin* field) select S from the dropdown list.
14& !elect -o* 'isplay.
15& 9eselect Start 9ode 8:er;rites 9ode i) TC' is (un.
16& Choose .
!creen eCATT -o* 'isplay <num%er= appears.
17& $xamine the log.
The log is structured hierarchically. $xpand the tree by clicking on the nodes. You will see
information about the system) test script) transaction) screens) and field values.
Foreground Processing
0"& Choose ) to go back to the script editor.
01& Choose .
00& Choose .
01& !elect Start 9ode 8:er;rites 9ode i) TC' is (un.
02& 4n the Start 9ode )or Command TC' field) select A from the dropdown list.
03& Choose .
04& !tep through the transaction by choosing to accept the >+ codes presented. You can change
field contents on the screens. *or example) try changing the name of the city. The change only
applies to this run.
At the end of the transaction) a new log is generated.
!rror Processing
05& Choose ) to go back to the script editor.
06& 4n the structure editor) expand the tree to find the field <R*,.+6/4*=R< of the first screen.
07& 9elete the contents 0****3 of the VA-I+ field.
1"& Choose .
11& Choose .
10& 4n the Start 9ode )or Command TC' field) select E from the dropdown list.
11& Choose .
This time) an error is caused by a preexisting record and the screen with the error is displayed.
12& Clear the Vendor field) and choose &
The execution continues and a new log is generated. 4n the absence of errors) the execution is
like background mode.
Preparing the Script for the %e"t Part of the Tutorial&
13& Choose ) to go back to the script editor.
14& Remove the error from the script.
15& Choose .
Result
$ach time you run the script you generate a vendor record and an eCATT log.
Part ' - Chaining a Series of Transactions
Use
The first transaction that you recorded) Create Vendor 0*+,-$. creates a customer record. Another
transaction) C,an*e Vendor 0*+,.3) allows you to modify an exiting customer record. 4n this transaction)
you will edit the address in a customer record that you created earlier.
You can chain these transactions together so that when you create a customer record) the record is
automatically passed to the second transaction for modification. To do this) you need to define the Vendor
number as an export parameter in the first transaction) and as an import parameter in the second
transaction. The Vendor number is passed between the transactions as a local variable.
Prerequisites
You have recorded transaction Create Vendor 0*+,-3 and edited the test script as described in parts -
and . of this tutorial.
Procedure
Recording Transaction F() and Creating an I*port Para*eter
1. Create a new test script. =ame it XYZ_FK0+ 0where 1Y2 are your initials3.
2. !tart recording transaction FK0+.
3. 4n the Vendor and Company Code fields) enter data of a vendor that you created earlier. You can
find this by looking in the log that was generated when you created the vendor.
4. !elect Address&
5. Choose .
6. $dit the name of the vendor to B Othr.
7. +eep choosing Enter until you return to the test script editor.
8. 4n the screen simulation) delete the contents of the Vendor field and choose .
A dialog box appears.
9. 4n the Param& +ame field) enter a name for the import parameter 0for this example use
,ENDOR_-./3 and in the ield contents field) enter the vendor number again.
10. Choose .
11. Choose ) to go back to the script editor.
The import parameter has been automatically entered in the structure editor.
12. 4n the parameter list) choose to display parameters. The input parameter appears
automatically. 4t has value 4 in the Visi%ility o) Parameter I>E>V field. 4f it is not visible choose to
refresh the list.
13. !ave the script as a local ob?ect.
Creating an !"port Para*eter
You have seen that transaction *+,- issues a message containing the vendor number and
company code. You can use the first variable part of the message) which contains the vendor
number) to provide the value for an export parameter.
14. 4n a new session) open test script 1Y2;*+,-.
15. 4n the parameter list) choose to display parameters. There are no parameters defined yet.
16. Choose .
17. 4n the Parameter field) enter ,ENDOR_EX/.
18. 4n the Visi%ility o) Parameter I>E>V field) enter E.
19. Choose Enter.
20. 4n the command editor) enter ,ENDOR_EX/ 0 1.S1. below the TC9 command. @5!- is an
eCATT variable. These always start with an ampersand 0@3. @5!- contains the first variable text
part of the last message from the transaction.
21. Choose .
Calling Scripts fro* +nother Script and Passing Values
22. 4n a new session) create a new test script. =ame it XYZ_C!A-N 0where 1Y2 are your initials3.
23. Choose Pattern) and in the Command field) choose (E from the dropdown list.
24. 4n the Test Script field) enter the name of the script in which you recorded transaction *+,-) and
choose .
4n the Inter)ace field) a system6generated name appears.
25. Accept the system6generated name by choosing .
The following appears in the command editor#
REF ' XYZ_FK01 ( XYZ_FK01_1 ).
26. 4n the command editor) position the cursor after the last statement. 'se Pattern to add a line to
the script so that it looks like this#
REF ' XYZ_FK01 ( XYZ_FK01_1 ).
REF ' XYZ_FK0+ ( XYZ_FK0+_1 ).
27. 4n the parameter list) choose to display parameters. There are no parameters defined yet.
28. Choose .
29. 4n the Parameter field) enter ,ENDOR_2OC.
30. 4n the Visi%ility o) Parameter I>E>V field) enter ,.
31. Choose Enter.
32. 4n the structure editor) assign the local variable to the import and export parameters.
33. !ave and execute the test script.
34. $xamine the log.
Result
You have generated a new vendor record and automatically altered it.

Part , - Loops- Conditions- and Inline +#+P
Use
eCATT allows looping and conditional processing. You can also include A(A% instructions within inline
A(A% blocks. 4nline A(A% allows you to access the power of the A(A% language from within the eCATT
environment.
Prerequisites
You have completed part of this tutorial.
Procedure
1& 9isplay the test script that you created earlier 0XYZ_C!A-N) in the script editor.
Looping
& 4n the command editor) use Pattern to enter a '8&&&E+''8 loop. 4n the Count field enter 3.
'& $dit the script so that the loop contains an R$* call to your first script. The script should look like
this#
DO ' 3 ).
REF ' XYZ_FK01 ( XYZ_FK01_1 ).
ENDDO.
REF ' XYZ_FK0+ ( XYZ_FK0+_1 ).
,& Choose ) to check the script.
.& $xecute the script and examine the log.
You have created three new records in table /*A-.
Conditional Processing
8ithin a 9>...$=99> loop you can use the $14T keyword to define a condition which) if satisfied)
causes the loop to be exited.
/& 4n the command editor) add the following line after the line containing the 9> keyword#
EX-T ' 12/C 0 3 ).
@/%C is an eCATT variable. 4t is the loop counter.
0& $xecute the script and examine the log.
The 9> loop now only creates two new records. 8hen the $14T condition is false) it is marked by
in the log) and when it is true) it is marked by .
You can use the 4*...$/!$4*...$/!$...$=94* keywords to perform conditional branching. 4n this
example) you will cause the first record created in the loop to be modified. The other records will
be left unchanged.
1& 4n the command editor) position the cursor before the $=99> statement and choose Pattern&
Choose I&&&E-SEI&&&E-SE&&&E+'I from the drop down list in the Command field) and in the
Condition field enter 12/C 0 1.
$dit the test script so that the R$* command to call the second script 0XYZ_FK0+3 is on the line
after the 4* command. Your test script should look like this#
DO ' 3 ).
EX-T ' 12/C 0 3 ).
REF ' XYZ_FK01 ( XYZ_FK01_1 ).
-F ' 12/C 0 1 ).
REF ' XYZ_FK0+ ( XYZ_FK0+_1 ).
E2SE.
END-F.
ENDDO.
2& $xecute the script and examine the log.
8hen the 4* condition is false) it is marked by in the log) and when it is true) it is marked by .
Inline +#+P
!tatements inside an A(A%...$=9A(A% block are not checked when you choose .
You cannot use eCATT statements inside inline A(A%. You can assign values to and from eCATT local
variables. 4n this example) you use A(A% to read a record from a table) and assign the contents of a field
of that record to a local variable.
1& Create a local variable call NA.E and of type C.
& Add the following lines to the script#
ABA/.
DATA 4a_#5a1 TY/E #5a1.
SE2ECT S-N62E 7 FRO. #5a1 -NTO 4a_#5a1.
NA.E 0 4a_#5a1-NA.E1.
ENDABA/.
2O6 ' NA.E ).
'& $xecute the script and examine the log.
4nline A(A% blocks are independent of each other. You can test this by adding the following code to your
test script#
ABA/.
Data n4_na8'1+9) t:; c <a#= *tst*.
7 n4_na8 0 4a_#5a1-NA.E1.
Na8 0 n4_na8.
ENDABA/.
2O6 ' NA.E ).
An asterisk at the beginning of a line denotes a comment line. The line is displayed in blue in the
command editor. Comment lines are never executed) but they are recorded in the log. Try executing the
test script with and without the asterisk.
The script generates an error in the second case.
Su**ar3
A false condition does not cause an error.
You can pass local variables to and from inline A(A%.
4nline A(A% blocks are independent of each other.

Part . - Using S3ste* 4ata
Use
You can run tests in remote systems. This is done through system data containers containing the re7uired
information about the R*C connections to the other systems. The test script itself is always on the local
system.
'sing a system data container in a test configuration is similar to using one in a test script. The system
data specified in the test configuration overrides the system data in the test script. Test configurations will
be covered later in this tutorial.
Prerequisites
You have completed the earlier parts of this tutorial.
You have the appropriate authori&ations for the R*C destinations that you will use. These R*C
destinations must contain transaction *+,-) and table /*A-. 4f this is not the case) you can still do this
tutorial by using the system that you are currently in as an R*C destination.
Procedure
Creating RFC 4estinations
1. 'se transaction !5AB to create an R*C destination. $nter the following information#
Field Co**ent
(C destination $nter a name for the R*C destination. *or example)
XYZ_RFC1 0where 1Y2 are your initials3.
Connection type *or a connection to an R/ !ystem) enter 3.
'escription $nter a short description.
-oad distri%& /oad balancing. !elect Ys.
Tar*et system $nter the name of the target system. *or example)
>1C.
9s*& ser:er $nter the host. You can find this by logging on to the
target system and choosing System Status&&&&
?roup $nter the group. *or example /?B2-C.
-an*ua*e $nter the logon language. *or example EN.
Client $nter the client. *or example) 000.
@ser $nter a user name that exists for the target system.
Pass;ord You need to enter the password for the user so that
tests in remote systems can be run automatically.
2.
3. Create a second R*C destination. Call it XYZ_RFC+ 0where 1Y2 are your initials3.
Creating S3ste* 4ata Containers
4. >n Extended Computer Aided Test Tool: Initial Screen) select System 'ata&
5. 4n the System 'ata field) enter a name for the system data container. =ame it XYZ_SDC1) where
1Y2 are your initials.
6. Choose .
You are now in the system data editor.
7. Choose the Attri%s tab and enter a short description in the Title field.
8. Choose the System 'ata tab.
A default target system is already defined. 4t is called =>=$. This target system is the current
system.
9. Choose .
10. 4n the Tar*et System field) enter a name for the target system. Call it TAR6ET_1.
11. 4n the (C 'estination field) enter the name 0XYZ_RFC13 of the R*C destination that you created
earlier.
12. Choose Enter.
The Instance 'escription field is automatically filled.
13. Create a second target system called TAR6ET_+ with the R*C destination XYZ_RFC+.
14. !ave the system data container.
Using a S3ste* 4ata Container in a Test Script
15. >pen your first test script 01Y2;*+,-3 for editing in the test script editor.
16. Choose the Attri%utes tab.
17. 4n the System 'ata Container field) enter the name of the system data container that you created
earlier 0XYZ_SDC1).
18. 4n the Tar*et System field) enter TAR6ET_1.
19. !ave and execute the test script.
20. $xamine the log.
There is an entry in the log that states the system in which the test script was executed.
21. 4n the command editor) add the following lines#
2FA1_1-2-FNR 0 1.S1.
C!ETAB ' 2FA1 ( 2FA1_1 ).
C!ETAB ' 2FA1 ( 2FA1_1 ( NONE ).
C!ETAB ' 2FA1 ( 2FA1_1 ( TAR6ET_+ ).
The first line assigns the message variable to the field /4*=R of the command interface /*A-;-.
You are using the same command interface for all the commands.
The first CC$TA( checks the table in the maintenance system. You assigned TARD$T;- to the
maintenance system. !econd CC$TA( checks the table in the current system E that is) the
system where eCATT and the test script are. The third CC$TA( checks the table in the system
specified by TARD$T;. in the system data container. 4f a CC$TA( finds a matching record) the
check is marked with a in the log. 4f there is no matching record) the check is marked by a in
the log.
22. Create a second system data container by copying XYZ_SDC1. =ame it XYZ_SDC+) where 1Y2
are your initials.
23. $dit 1Y2;!9C. so that all the R*C 9estination fields contain =>=$.
24. 4n the test script) choose the Attri%utes tab and enter XYZ_SDC+ in the System 'ata Container
field.
25. $xecute the test script. *rom the log) you should see that the target systems have changed to the
current system.
The point to remember is that the names of the target systems remain the same in the test script. 4t is the
R*C destinations that are assigned to those names that are changed in the system data containers.
Su**ar3
A system data container contains one or more target systems.
A target system specifies an R*C destination.
To execute a test script in another system you enter a system data container and a target system.
You can change the target systems of eCATT commands by swapping in different system data
containers.
Part / - Test 4ata Containers
Use
Test data containers allow you to maintain data variants independent of test scripts. They contain data for
use with the input parameters of test scripts.
>nly the parameters specified in a test data container that have the same name and type as those in the
test script will be accessible.
A test data container need not have the same number of parameters as the test script. 5issing
parameters will have default values supplied by the test configuration. $xtra parameters are ignored.
You will now create a new test script and some test data containers that you will use latter in a test
configuration.
Procedure
-. Create a new test script. =ame it XYZ_,AR-ANTS 0where 1Y2 are your initials3.
.. 4n the parameter list) create five parameters of A(A% type C as shown in the table below#
Para*eter Value Visibilit3 5I6!6V7 4ata T3pe in
+#+P
Length
A2/!A 1 - C 1+9
BETA + - C 1+9
6A..A 3 - C 1+9
DE2TA 0 E C 1+9
O.E6A @ , C 1+9
. 4n the command editor) add the following instruction#
,& DE2TA 0 A2/!A A BETA A 6A..A A O.E6A.
A. !ave the test script.
:. >n Extended Computer Aided Test Tool: Initial Screen) select Test 'ata and enter a name for the
test data container. 4n this case use XYZ_TD1 0where 1Y2 are your initials3.
F. Choose .
G. The test data editor appears.
B. Choose the Attri%utes tab) and maintain the attributes.
-,. Choose the Parameters tab. >bserve that it is similar to the parameter editor in the test script
editor. Cowever) there is no Visi%ility o) Parameter #I>E>V$ field.
--. Create the parameters as shown in the table below#
Para*eter Value 4ata
T3pe in
+#+P
Length
A2/!A 11 C 1+9
BETA ++ C 1+9
6A..A 33 C 1+9
E/S-2ON @@ C 1+9
-.. Choose the Variants tab.
-. You see that the $CATT9$*A'/T variant has parameters A/%CA) ($TA) DA55A) and
$%!4/>= with the values that you entered on the Parameter tab. You can create other variants
that have different values for these parameters.
-H. Create variants as shown in the table below#
Variant +LP8+ #!T+ 9+::+ !PSIL;%
ECATTDEFA?2T 11 ++ 33 @@
,1 1 @ + @
,+ B

@ &
,3 C 3

&
-A. Choose ) and save as a local ob?ect.
-:. Create a second test data container. =ame the new test data container XYZ_TD+) where 1Y2 are
your initials. 5ake this test data container similar to the first) but use different values.
Su**ar3
9ata containers contain data variants. >nly parameters of the same name and type as those in a test
script will be usable with that test script.

Part 0 - Using Test Configurations and Variants
Use
A test configuration contains references to the test script) system data) and test data needed to execute a
test.
Prerequisites
You have created a test script and a test data container as described in part : of this tutorial. You have
created a system data container as described in part A of this tutorial.
Procedure
Create a Test Configuration
1& >n the Extended Computer Aided Test Tool: Initial Screen) select Test Con)i*uration and enter a
name for the test configuration. Call it XYZ_TC1 0where 1Y2 are your initials3.
& Choose .
The test configuration editor appears.
'& Choose the Attri%ute tab and enter the re7uired information in the Title and Component fields.
,& Choose the Con)i*uration tab.
.& 4n the Test Script field) enter the name 0XYZ_,AR-ANTS3 of the test script you created in part :.
/& 4n the System 'ata Container field) enter the name of system data container 0 XYZ_SDC1 3 that
you created in part A of this tutorial.
0& 4n the Tar*et System field) enter NONE.
1& Choose . and save as a local ob?ect.
Create a Variant :anuall3
2& Choose the Variants tab.
You see that the $CATT9$*A'/T variant has the parameters A/%CA) ($TA) and DA55A. The
parameters have the values specified in the test script. >nly input parameters in the test script
are visible in the test configuration. You can create other variants that have different values for the
parameters.
1)& Choose to create a new variant. =ame it ,AR1.
11& Choose to create a new variant. =ame it ,AR+.
1& $nter values in some fields of the variants as shown in the table below#
Variant +LP8+ #!T+ 9+::+
ECATTDEFA?2T 1 + 3
,AR1 3

,AR+ D 3 &
1'& Choose .
1,& Choose .
The Start 8ptions dialog box appears.
1.& /eave the Variant and System fields empty.
1/& Choose .
10& $xamine the log. The script has been run three times" once for each variant. The default values
have been used where no value has been specified.
11& $xecute the test configuration again. This time enter ,AR1 in the Variant field of the start options.
>nly the selected variant is tested.
Create a Variant fro* a Test 4ata Container
12& 4n the test configuration editor) choose the Con)i*uration tab.
)& Choose .
1& 4n the Test 'ata Container field) enter XYZ_TD1.
& 4n the Alias field) enter A1. The alias is used on the Variants tab to refer to this test data.
'& =ow add test data container XYZ_TD+ with alias A+.
,& Choose the Variants tab.
.& Choose .
The 8i&ard appears. The left half of the screen displays the variants in a test data container. The
right half of the screen displays the variants in the test configuration.
/& !croll through the test data containers using and .
0& !elect variant I from test data container A- and choose Attac, as Variant. >nly the
parameters in the test data container that match those of the test script are appended.
1& Choose .
The variant is now displayed on the Variants tab.
2& $xecute the script and look at the log.
All variants have been executed.
Su**ar3
4f no value is specified for a parameter in a variant) the value from the $CATT9$*A'/T variant is used.
Ialues can be entered directly into a variant) or be held as references to values in test data containers.
'sing the start options) you can choose to execute using only one variant.
Part 1 - Versions
Use
8hen there are several versions of a referenced test script) eCATT automatically finds the one
appropriate to the software component and release level of the target system.
Procedure
-. >n the Extended Computer Aided Test Tool: Initial Screen) select Test Script.
.. 4n the Test Script field) enter the name of the test script that you created in part A of this tutorial
0XYZ_,AR-ANTS3.
. 4n the Versions field) enter +.
H. Choose .
A. >n the Attri%utes tab) enter a title. *or example Scon" ,rsion.
:. Choose the Editor tab.
The command editor is empty.
The parameter list has all the import and export parameters of the first version. You should not
change the names and types of these parameters. Cowever) you may change the default values.
/ocal variables are not retained from the first script. You are free to define any new local
variables.
F. Create a new local variable called E/S-2ON with a default value 1.
G. Create a new set of commands in the command editor.
DE2TA 0 A2/!A A BETA A 6A..A A E/S-2ON.
C!E,AR ' DE2TA EF 13 ).
B. $xecute this test script.
-,. =ow try to execute the test configuration that you created earlier. 4t does not work. There are now
two versions of the test script and the test configuration does not know which one it should use.
You need to specify the software component and release for which each version is valid. You do
this on the Attri%utes tab of each version.
To find information about software components) choose System A= Status. and in t,e System
Status dialog box choose .
--. 4n the first version of the test script) enter the software component and release of the system that
you are running eCATT in. *or example) SA/_BAS-S and &+0. The same software component is
now also in the second version. Try to enter the same release information. This does not work 6
you cannot enter the same combination of software component and release information that you
have specified in another version of the test script. =ow enter a different release 0for example
&303.
-.. 5ake the target system) of the test configuration) the system that you are running eCATT in.
-. $xecute the test configuration.
-H. $xamine the log and determine which version of the script has been executed.
-A. Change the target system to one that matches the software component and release specified in
the second version of the test script.
-:. $xecute the test configuration.
Su**ar3
The implementation can be totally different from version to version.
The import and export parameters are the same in all versions.