reminder call today + test event log use cases

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Date:  Monday, 15 May 2006

Time:  11:00am - 12:00pm PT

 

Event Description:

Toll only :  1-512-225-3050

Participant code: 953641

 

Agenda:

1. status of ebBP deplt template: feedback from ebBP TC and latest updates to be done (mapping table-schema, use of XInclude).

2. Test script language upgrade:

- review of overall requirements motivating upgrade, Business Transaction test cases.

- focus on test event log capability (see below)

3.Test Assertions guideline and what W3C QA IG is doing.

 

 

Test Case scripting: “reading” the event log:

How does GetEvent (formerly Getmessage) work:

(see item 6 in past email on test scripting)

     

Use cases in "getting [test] events" within a Test Case. Events are here messages

sent by the other party.

 

1. test case keeps going if a response message correlating (condition R) with previous message

is received within time window T. The received message must then satisfy some condition C.

-> GetEvent("lasting" with max duration T - the filter does only R, not C)

If GetEvent succeeds (returns positive result), test case proceeds with checking C.

 

2. test case fails if an Error message (condition E) related to previous message (condition R),

is received within time window T.

-> GetEvent("lasting" with max duration T - the filter does checks E and R)

If GetEvent returns positive result, test case fails.

 

3. test case succeeds only if exactly 3 message of a particular profile (condition P) e.g. resulting

from resending mechanism in reliable messaging have been received, within time window.

-> GetEvent("scheduled" at the timeout of window (now+T), "instantaneous" execution, checks P)

If GetEvent returns positive result (exactly 3 messages that satisfy P), test case succeeds.

 

-Jacques