Docstoc

Acceptance Test Plan Acceptance

Document Sample
Acceptance Test Plan Acceptance Powered By Docstoc
					                    Acceptance Test Plan
                     Team B.E.E.F.E.A.T.E.R.



Nick Canzoneri   Adam Hamilton    Georgi Simeonov   Nick Wolfgang

                          Matt Wozniski
    Date: May 1, 2009


 Date                    Description           Revision
December 2, 2008        Initial version       1
February 17, 2009       First revision        2




                                          i
Contents
1 Introduction                                                                                                                                                                                  1
  1.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                                                                        1
  1.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                                                                        1
  1.3 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                                                                        1

2 Test Approach and Constraints                                                                                                                                                                 1
  2.1 Introduction . . . . . . . . . . .                       . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   1
  2.2 Roles and Responsibilities . . .                         . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   1
  2.3 Testing Approach . . . . . . . .                         . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   1
      2.3.1 Goals of the Acceptance                            Test        .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   1
      2.3.2 Types of Tests . . . . .                           . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   1
  2.4 Assumptions . . . . . . . . . .                          . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   2
  2.5 Exclusions . . . . . . . . . . . .                       . . .       .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   2

3 Testing Procedure                                                                                                                                                                             2
  3.1 Introduction . .     .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   2
  3.2 Entry Criteria .     .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   2
  3.3 Exit Criteria .      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   2
  3.4 Reporting . . .      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   3

4 Test Cases                                                                                                                                                                                     3
  4.1 Hearts Game . . . . . . . . . . . . . . . . . . . . . . . .                                                       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
      4.1.1 Requirements 5.1.3.1.1-2 . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
      4.1.2 Requirements 5.1.3.1.2-3 . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
      4.1.3 Requirements 5.1.3.1.4-5 . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
      4.1.4 Requirements 5.1.3.1.6-9 . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
      4.1.5 Requirement 5.1.3.1.10 . . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    3
  4.2 Document Reviewer . . . . . . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    4
      4.2.1 Application Login . . . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    4
      4.2.2 Session Creation . . . . . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    4
      4.2.3 Portal Page . . . . . . . . . . . . . . . . . . . . .                                                       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    4
      4.2.4 In the Session . . . . . . . . . . . . . . . . . . . .                                                      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    5
  4.3 Instant Messaging Client . . . . . . . . . . . . . . . . . .                                                      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    6
      4.3.1 Creating an account and registering a user name                                                             .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    6
      4.3.2 Connecting to the Service . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    6
      4.3.3 Connecting to the Service as a guest . . . . . . .                                                          .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    6
      4.3.4 Creating a group chat . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    6
      4.3.5 Inviting other users to a chat . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
      4.3.6 Receiving a chat invite . . . . . . . . . . . . . . .                                                       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
      4.3.7 Conversation . . . . . . . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
      4.3.8 Sending a URL through a Conversation . . . . .                                                              .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
      4.3.9 Adding another user to a buddy list . . . . . . .                                                           .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
      4.3.10 Setting active and away state . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    7
  4.4 Windowing Library . . . . . . . . . . . . . . . . . . . . .                                                       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    8
      4.4.1 Window Attributes . . . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    8
      4.4.2 Window Methods . . . . . . . . . . . . . . . . . .                                                          .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    8
      4.4.3 Window Events . . . . . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    9
      4.4.4 generic windows . . . . . . . . . . . . . . . . . .                                                         .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .    9
  4.5 Multi-Threading . . . . . . . . . . . . . . . . . . . . . .                                                       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   11
      4.5.1 Semaphore Data Structure . . . . . . . . . . . .                                                            .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   11
      4.5.2 Thread Yield . . . . . . . . . . . . . . . . . . . .                                                        .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12



                                                                                   ii
      4.5.3   Thread Join . . . . . . . .    .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12
      4.5.4   List Joined Threads . . .      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12
4.6   Event   Handling . . . . . . . . . .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12
      4.6.1   Register Event Handler .       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12
      4.6.2   Unregister Event Handler       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   12




                                                             iii
1       Introduction

1.1     Objectives
This document defines the Acceptance Test Plan and Test Cases for the B.E.E.F.E.A.T.E.R. project.


1.2     References
Software Requirements Specification for B.E.E.F.E.A.T.E.R.


1.3     Glossary
Unit Test Unit tests are highly granular tests that attempt to test all possible paths through a software
     system and observe that the expected behavior occurs for each case.


2       Test Approach and Constraints

2.1     Introduction
This section describes how the Acceptance Test of the B.E.E.F.E.A.T.E.R project will be performed
and evaluated.


2.2     Roles and Responsibilities
During testing, the following roles will be assumed:
    • Test Team Leader: responsible for facilitating the testing
    • Client Representative: responsible for overseeing the Acceptance Testing from the perspective of
      a developer who will use the framework
    • Tester: responsible for executing the test cases


2.3     Testing Approach
2.3.1    Goals of the Acceptance Test

The acceptance test is a final test of the system, to be executed after the software passes all of the
more extensive unit tests and has been successfully integrated. The acceptance test will consist of a set
of selected tests which demonstrate that the system complies with all requirements, but will not be as
exhaustive as the unit and integration testing.


2.3.2    Types of Tests

The acceptance test will be largely compromised of user walkthroughs of meaningful scenarios to ensure
that the software behaves as expected.
Our system tests will also include timing and stress tests to ensure that our application meets perfor-
mance requirements. As the acceptance test is a higher level, final test, acceptance testing will not




                                                    1
include specific performance testing but will seek to demonstrate that the overall performance of each
task is adequate.


2.4     Assumptions
It is assumed that the project has already passed unit, integration, and system testing before acceptance
testing begins.
The acceptance test plan will cover:
    • The functional requirements of the system, as described in the Software Requirements Specification
    • All of the high priority features of the sample applications


2.5     Exclusions
The acceptance test will not cover:
    • The specific non-functional requirements of the system, except where there is a noticeable perfor-
      mance or usability problem obvious in the testing
    • Integrity of the source code
    • Usability of the developer API


3     Testing Procedure

3.1     Introduction
This section lists the criteria for testing to begin and to end, and the reporting procedure for issues
discovered during testing.


3.2     Entry Criteria
Before an acceptance test can begin, the following conditions must be met:
    1. B.E.E.F.E.A.T.E.R has completed unit, integration, and system testing
    2. A testing environment running the latest copy of the B.E.E.F.E.A.T.E.R framework has
       been configured
    3. The sample applications have been installed in the testing environment
    4. The Software Requirements Specification has been updated to reflect the most current un-
       derstanding of the software requirements
    5. The consent of the client and test team leader have been obtained


3.3     Exit Criteria
The acceptance test ends successfully when:
    • All Priority 1 requirements have been met in accordance with the Software Requirements Spec-
      ification
The acceptance test fails and ends when:



                                                    2
    • Any Priority 1 requirement deviated from the expected behavior
    • The client representative feels that an area of extremely poor performance or usability in a critical
      area has made the system unacceptable


3.4     Reporting
All problems discovered during the test are to be reported to the test team leader. At the end of the
test, a test report will be submitted to the project team leader describing the issued that need to be
addressed.


4       Test Cases

4.1     Hearts Game
4.1.1    Requirements 5.1.3.1.1-2

Precondition User begins the hearts game application
Action User selects a table to play at
Postcondition User is placed at the table waiting for the next game to start or if there is an ongoing
     game the user must wait for the game to end


4.1.2    Requirements 5.1.3.1.2-3

Precondition User is at a table
Action User stands up from (leaves) a table
Postcondition User is removed from the table and presented with a list of other tables to join or if
     the game is in progress the user is not allowed to leave until the game is completed


4.1.3    Requirements 5.1.3.1.4-5

Precondition A game has started
Action Cards are dealt to each user from the deck
Postcondition The user has the proper number of randomly selected cards from the deck


4.1.4    Requirements 5.1.3.1.6-9

Precondition A game of hearts is started
Action A round of hearts is played
Postcondition The user can see the cards in play and the score changes. Only correct plays were
     made.


4.1.5    Requirement 5.1.3.1.10

Precondition A game of hearts has ended




                                                     3
Action The user is shown the final game scores
Postcondition The user is ready to exit the game or begin a new game


4.2     Document Reviewer
4.2.1     Application Login

4.2.1.1    Requirement 5.2.3.1.1

Precondition User goes to applications login screen
Action User provides authentication info
Postcondition User is presented with application’s portal screen


4.2.2     Session Creation

4.2.2.1    Requirement 5.2.3.1.2:

Precondition User is at application’s session creation screen
Action User clicks upload document
Postcondition Document is uploaded and associated with the new session


4.2.2.2    Requirements 5.2.3.1.3-5:

Precondition User is at application’s session creation screen
Action User inputs an email of a person to be invited and clicks invite
Postcondition Session will be added to users available sessions
Conditional Postcondition If user is not in system, authentication information will be generated by
    the system and sent to the provided email


4.2.2.3    Requirement 5.2.3.1.6:

Precondition Session creator is at session information page
Action Session creator clicks uninvite on a member of the session
Precondition Member shall not be able to view the session anymore


4.2.3     Portal Page

4.2.3.1    Requirement 5.2.3.1.10:

Precondition User is at session portal page
Action User mouses over a session name
Postcondition Information will overlay the document originating at the mouse cursor detailing meta-
     data of the document




                                                 4
4.2.4     In the Session

4.2.4.1    Requirement 5.2.3.1.12:

Precondition User is within a session viewing the session windows
Action User initiates the mouse down event in the lower right hand corner of the window
Postcondition Window is enlarged or shrunk in the direction of the movement of the mouse until the
     mouse up event occurs


4.2.4.2    Requirements 5.2.3.1.13:

Precondition User is within a session viewing the session windows
Action User initiates mouse down event in the title bar of the window
Postcondition Window follows the motion of the mouse until the mouse up event occurs


4.2.4.3    Requirement 5.2.3.1.14:

Precondition User is within a session viewing the session windows
Action User clicks the icon in the window title bar that signifies window closure
Postcondition The window is no longer visible on the page


4.2.4.4    Requirement 5.2.3.1.15:

Precondition User is within a session viewing the session windows
Action User clicks the icon in the window title bar that signifies window minimization
Postcondition All of the window except for the title bar becomes hidden and the icon for minimization
     becomes the icon for maximization


4.2.4.5    Requirement 5.2.3.1.21:

Precondition User is within a session
Action User highlights text in the document window
Postcondition A comment creation text box appears


4.2.4.6    Requirements 5.2.3.1.22-23:

Precondition User entered text in comment creation box
Action User clicks create comment
Postcondition User’s comment is now visible to all members of session


4.2.4.7    Requirement 5.2.3.1.24:

Precondition User has entered text in to the chat window text box
Action User hits the Enter key



                                                 5
Postcondition User’s text appears in the chat communication window visible to all users of the session


4.2.4.8    Requirement 5.2.3.1.25:

Precondition A session is being used by members
Action Members create a comment
Postcondition The changes are stored by the application


4.3     Instant Messaging Client
4.3.1     Creating an account and registering a user name

4.3.1.1    Requirements 5.3.3.1.12

Precondition A user goes to the application’s create an account screen
Action Provides user information
Postcondition A user is presented with the application’s Login screen


4.3.2     Connecting to the Service

4.3.2.1    Requirements 5.3.3.1.2-3, 5.3.3.1.7

Precondition A user goes to the application’s Login screen
Action User enters valid login information
Postcondition A user is presented with the applications buddy list


4.3.3     Connecting to the Service as a guest

4.3.3.1    Requirements 5.3.3.1.11

Precondition A user goes to the application’s Login screen
Action A user Selects log in as Guest
Postcondition A user is presented with the applications buddy list


4.3.4     Creating a group chat

4.3.4.1    Requirements 5.3.3.1.5, 5.3.3.1.6, 5.3.3.1.10

Precondition A user wants to create a group chat while logged in
Action A user selected the create a group chat option and enters a chat name
Postcondition A group chat is created and presented to the user




                                                  6
4.3.5     Inviting other users to a chat

4.3.5.1    Requirements 5.3.3.1.5, 5.3.3.1.6, 5.3.3.1.10

Precondition A user is in a group chat and wants to invite a user from their buddy list
Action A user selects a user from their buddy list and invites them to the chat
Postcondition The invited user gets the invite


4.3.6     Receiving a chat invite

4.3.6.1    Requirements 5.3.3.1.5, 5.3.3.1.10

Precondition A user sent a chat invite
Action The invited users accepts the invite
Postcondition The user joins the group chat and is presented with a chat room


4.3.7     Conversation

4.3.7.1    Requirements 5.3.3.1.1, 5.3.3.1.4, 5.3.3.1.10

Precondition A user is in a conversation with another user
Action A user types a message into the text box and presses enter
Postcondition The message disappears from the text box and appears in the message box for both
     users


4.3.8     Sending a URL through a Conversation

4.3.8.1    Requirements 5.3.3.1.9

Precondition A user is in a conversation with another user
Action A user types and sends a message that contains a URL
Postcondition The URL appears in the message box as clickable link that opens in a new window or
     tab


4.3.9     Adding another user to a buddy list

Precondition The user is logged into the Instant message application
Action The user selects the add user option and types in a valid screen name
Postcondition The user of the screen name is added to the buddy list


4.3.10     Setting active and away state

4.3.10.1    Requirements 5.3.3.1.8

Precondition The user is logged into the Instant message application
Action The user selects the status option and sets an away state message



                                                 7
Postcondition The user then goes into the desired state with the message being displayed


4.4     Windowing Library
4.4.1     Window Attributes

4.4.1.1     Requirements 4.2.1.2.1

Precondition A window is created
Action Code is executed to access an attribute of the specified window
Postcondition The current correct value of the attribute shall be returned


4.4.2     Window Methods

4.4.2.1     Requirements 4.2.1.2.2

4.4.2.1.1    Collapse

Precondition A window is created
Action Code is executed calling the collapse method
Postcondition The title bar becomes the only viewable area of the window


4.4.2.1.2    Maximize

Precondition A window is created
Action Code is executed calling the maximize method
Postcondition The window area expands to fill the container window


4.4.2.1.3    Minimize

Precondition A window is created
Action Code is executed calling the minimize method
Postcondition The title bar becomes the only viewable area of the window and moves to the bottom
     left of the container window


4.4.2.1.4    Hide

Precondition A window is created
Action Code is executed calling the hide method
Postcondition The window no longer is visible to the user


4.4.2.1.5    Show

Precondition A window is created
Action Code is executed calling the show method



                                                  8
Postcondition The window shall be visible to the user


4.4.3     Window Events

4.4.3.1     Requirements 4.2.1.2.4

Precondition A window is created
Action Code is executed or user action that causes the window event to occur
Postcondition The call back function of the event is executed


4.4.4     generic windows

4.4.4.1     Requirements 4.2.1.2.6

Unless specified, the precondition for all of the items in this section is a client browser and server
environment where our scaffold is in place.


4.4.4.1.1    ok/cancel

Action Code is executed to create ok/cancel window
Postcondition ok/cancel window is created
Precondition An ok/cancel window is created
Action User hits ok
Postcondition Window closes and ok is passed to callback function
Precondition ok/cancel window is created
Action User hits cancel
Postcondition Window closes and cancel is passed to callback function


4.4.4.1.2    button+ window

Action Code is executed to create button+ window
Postcondition Button+ window is created
Precondition Button+ window is created
Action User clicks any of the buttons displayed in the window
Postcondition The window closes and the value of the button is passed to the call back function


4.4.4.1.3    time picker window

Action Code is executed to create a time picker window
Postcondition A time picker window is created
Precondition A time picker window is created
Action User fills in data fields and clicks finish button
Postcondition Window closes and data in data fields is returned to callback function



                                                 9
Precondition Time picker window is created
Action User clicks cancel button
Postcondition Window closes and no data is passed to call back function


4.4.4.1.4   date window

Action Code is executed to create a date window
Postcondition A date picker window is created
Precondition A date picker window is created
Action User fills in data fields and clicks finish button
Postcondition Window closes and data in the data fields is passed to call back function
Precondition Date picker window is created
Action User clicks cancel button
Postcondition Window closes and no data is passed to call back function


4.4.4.1.5   date+ window

Action Code is executed to create a date+ window
Postcondition A date+ window is created
Precondition Date+ window is created
Action User fills in date fields and clicks finish button
Postcondition Window closes and the dates are passed to call back function
Precondition Date+ window is created
Action User clicks cancel button
Postcondition Window closes and no data is passed to call back function


4.4.4.1.6   list window

Action Code is executed to create a list window
Postcondition A list window is created
Precondition List window is created
Action User reorders items in list and clicks finish button
Postcondition Window closes the reordered list is passed to call back function
Precondition List window is created
Action User clicks cancel button
Postcondition Window closes and no data is passed to call back function


4.4.4.1.7   progress bar

Action Code is executed to display a progress bar
Postcondition A progress bar is displayed



                                                  10
Precondition A progress bar is displayed
Action The event the progress bar is monitoring is updated
Postcondition Updated status is reflected in the progress bar
Precondition Progress bar is displayed
Action Event the progress bar is monitoring is completed
Postcondition Progress bar status changes to 100% and closes
Precondition Progress bar is displayed
Action Event the progress bar is monitoring is canceled
Postcondition Progress bar status changes to 0% and closes


4.4.4.1.8    slider window

Action Code is executed to create a slider window
Postcondition A slider window is displayed
Precondition Slider window is displayed
Action User modifies the slider bar
Postcondition Selected value of the slider window is updated to represent the graphical value
Precondition Slider window is displayed
Action User enters a value into the selected value field
Postcondition The graphical slider changes to represent the data in the selected value field
Precondition Slider window is created
Action User clicks finish button
Postcondition Window closes and data represented in the selected value field(s) is passed to the call
     back function
Precondition Slider window is created
Action User clicks the cancel button
Postcondition Window closes and no data is passed to call back function


4.5     Multi-Threading
4.5.1     Semaphore Data Structure

4.5.1.1     Requirement 4.2.3.1

Precondition A constructed semaphore data structure
Action Attempt to access a shared resource simultaneously
Postcondition The shared resource only having been accessed one at a time




                                                 11
4.5.2     Thread Yield

4.5.2.1    Requirement 4.2.3.2

Precondition One or more running threads
Action Execute yield on a particular thread
Postcondition The thread that yield was executed on shall have stopped execution until other threads
     have finished


4.5.3     Thread Join

4.5.3.1    Requirement 4.2.3.3

Precondition Two or more running threads
Action Execute join on a particular thread
Postcondition The thread that join was executed on shall not continue execution until the currently
     executing thread shall have stopped execution.


4.5.4     List Joined Threads

4.5.4.1    Requirement 4.2.3.4

Precondition Joined threads
Action Execute the code to list joined threads
Postcondition A list of threads that are joined


4.6     Event Handling
4.6.1     Register Event Handler

4.6.1.1    Requirement 4.2.4.1

Precondition An event handler registered to an event
Action The event occurs
Postcondition The code in the event handler is executed


4.6.2     Unregister Event Handler

4.6.2.1    Requirement 4.2.4.2

Precondition An event handler registered to an event
Action Execute code to unregister the event handler and event occurs
Postcondition Event handler code is no longer executed when event occurs




                                                  12

				
DOCUMENT INFO