cancel
Showing results for 
Search instead for 
Did you mean: 

eCATT: making TCD not fail on error messages

markus_theilen
Participant
0 Kudos

Hi!

I want to use eCATT for testing authority checks. Therefore, I recorded a TCD session (no controls in the dynpros) and played it back with intended wrong parameters. It is right for the transaction to respond with an error message and I want the test case to be green. Problem is, it is red.

I tried to put the TCD command into a MESSAGE...ENDMESSAGE block with matching message rules, but this does not help at all.

Has anyone a clue what to do to make the test not fail..? I mean, the call should fail, because the current user is not allowed to use the report behind the transaction and I want to verify this.

Or has anyone a nice example of a test case testing for a failing authority check ?

Accepted Solutions (1)

Accepted Solutions (1)

markus_theilen
Participant
0 Kudos

Hi again!

Found a solution, but am not sure whether it is a good on.

Using the obsolet command ON_LAST_MESSAGE_CHECK with the expected error message number, I get what I want: The TCD command fails, because it should so and the test case is green.

But the fact that this command is flagged as obsolet makes me wonder, what could be the better solution. In the documentation there is no hint on this. As said before, putting the TCD in a MESSAGE block with a appropiate message rule is no solution.

Former Member
0 Kudos

Markus,

which release are you working with?

In 6.20, you have to use ON_LAST_MESSAGE_CHECK ( * ).

In 6.40, you can use a MESSAGE...ENDMESSAGE block with the following rule in the MESSAGE statement:

MODE: 'A'

MSGTYP: 'E'

(all other fields blank)

markus_theilen
Participant
0 Kudos

Hi!

Sorry, I forgot to post the version of the WAS in the first post. We are running 6.20, so we have to stick to ON_LAST_MESSAGE_CHECK, it seems.

Thank you for your helpful answer!

Answers (0)