Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Functional Unit Testing of Derived Roles in ECC 6.0

Former Member
0 Kudos

Hello, not sure this is in the right forum so I took a chance. I was wondering if anyone knew of any good resources to reference for testing of dervied roles in ECC 6.0. The roles will need to be tested to ensure the transaction codes and auth objects are built properly, both positive and negative testing. Thank you.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

The testing strategy depends on what exactly you want to test. Let me illustrate by an example:

1.Suppose you have 5 derived roles . We assume that roles are different at company code or plant level only.

Let R1, R2, R3, R4 and R5 be your roles and C1, C2,C3, C4 and C5 be your company codes.

2.It is advisable that you not only execute the transaction codes but also input some field values wherever relevant and

try to do this in a test system which has meaningful data. Only then your testing will be complete.

3. Say role R1 has T-code T1, T2, T3. In our case a positive testing will mean that you can properly execute T1,T2 and T3 for

company code C1 and a negative testing is that the same fails for C2, C3...C5.

4. A process to save testing time will be to test the functions of only one derived role, make sure that any object level authorization issue is resolved, accordingly add authorizations to other derived roles (R2,R3 etc) and then via AGR_1252 table make sure that plant/company codes are properly maintained (this is the cross checking part).

Try to make a neat excel with all details beforehand. This will be helpful.

Cheers,

Arka.

3 REPLIES 3

Former Member
0 Kudos

Hi,

The testing strategy depends on what exactly you want to test. Let me illustrate by an example:

1.Suppose you have 5 derived roles . We assume that roles are different at company code or plant level only.

Let R1, R2, R3, R4 and R5 be your roles and C1, C2,C3, C4 and C5 be your company codes.

2.It is advisable that you not only execute the transaction codes but also input some field values wherever relevant and

try to do this in a test system which has meaningful data. Only then your testing will be complete.

3. Say role R1 has T-code T1, T2, T3. In our case a positive testing will mean that you can properly execute T1,T2 and T3 for

company code C1 and a negative testing is that the same fails for C2, C3...C5.

4. A process to save testing time will be to test the functions of only one derived role, make sure that any object level authorization issue is resolved, accordingly add authorizations to other derived roles (R2,R3 etc) and then via AGR_1252 table make sure that plant/company codes are properly maintained (this is the cross checking part).

Try to make a neat excel with all details beforehand. This will be helpful.

Cheers,

Arka.

0 Kudos

Thanks very much,

Former Member
0 Kudos

Isnt the testing team or functional teams supposed to give the appropriate business processes for testing.. They usually do based on which Security teams can build test cases for scenarios. Since it changes from client to client, generic resources are scarce on the internet..

~Sri