Community
Participate
Working Groups
This reentry type should handling the following issue: If I want to use the same event handlers with reentry type RETURN for different Use Cases, I have to define it in every Use Case redundantly. If I could use the parent TC or TS with a new reentry type called NEXT I only need to write the EH once. NEXT is working like RETURN after it has stepped down in the TC stack trace one step.
This idea has been discussed and found to be generally good. In terms of the functional description, something along the lines of: "jumps to the next child of the Test Case in which the Event Handler is nested" This would allow the following: TC: User Story Login -EH: restart and "Next" - TC: Login successfully - TC: Login unsuccessfully case 1 - TC: Login unsuccessfully case 2 If and error occurs in TC "Login unsuccessfully case 1" which is not already dealt with in that TC, then the "Next" Event Handler would be activated. The application would restart and "Login unsuccessfully case 2" would be executed. In short, we would have the same structural possibility as with our "Return" Event Handlers, but without the necessity to place the Event Handler in each independent Test Case. Possible counter arguments: readability and overview / being able to understand which Test Cases are covered by which Event Handler.
