-
Junior Member
Test Conditions
Can anyone tell me how to write test conditions using use cases
-
Expert Member
Re: Test Conditions
Hi Reks,
An usecase is basically a document explaining the functional flow within a particular module and indicating the actors / entities present within such a flow.
For instance if you consider an Yahoo Mail Page, the use case would basically describe 3 possible flows -
1) Entity enters User ID and Valid Password; gets redirected to Inbox page
2) Entity enters Invalid UserID or Invalid Password; gets redirected to forgot Password / Login page
3) Entity is a new user and access Registeration page
Now when deriving testcases out of a usecase, we use these conditions and create a testscenario for each of these condition. These scenarios are covered as Testcases which enlist the action steps in detail.
So we would have a testcase for valid Login, Invalid Login, Registeration.
NOTE : Registeration process could be a seperate Usecase. So in such a case, our testcase would limit to only displaying the Registeration page to the new User.
Cheers.
-
Re: Test Conditions
Use case is a base document prepared out from the Functional requirement specification and is used by both the Developers and the Testers. Use case document will have the information regarding how the flow will occur in the Application under Test. There are three types of flows:
1. Basic Flow
2. Alternate Flow and
3. Exceptional Flow
Use case may be a pictorial representation of the requirement or a document with the flow of activities.
All the test cases are derived out from the Use case. For a application under Test the Test scenarios are identified for all the three flows. Exceptional flow is basically to test system behaviour in case of error flow.
As a first step, test scenarios are identified from the Use case for which the test cases are prepared.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules