Writing Test Case Using Use cases

Writing Test Case Using Use cases

Use case: Tag Notification to the Group
Confidence:Y
Exec Method: M
TestPlan:
Build #:
Pass/Fail:
TestScript:
CR#:
Comment:
TestCase:
Based On: UC

TestData:
Specific Preconditions
· Configure HMI and ensure that the alarm has been generated
· Configure three operators in the “ON CALL” list
· Every operator in the group should have configured with a voice phone number
Basic course

Input Specifications
Output Specifications
1. Configured HMI generates an alarm and SCADAlarm calls the configured operator.
2. Verify the number of retries without answering the call

o The number of retries equals to the value of “Number of retries before moving on to the next call” configured in the menu Configuration>>System Parameter>>Retrying tab
3. Verify that the call is diverted to the next person in the call list/schedule after exceeding the value in the menu Configuration>>System Parameter>>Retrying tab ----Number of retries before moving on to the next call
o Application should divert the call to next person as per call list/schedule depending on the alarm condition
4. The Second operator receives the call on the configured number
o The Second Operator is greeted if the greeting file is configured
5. Enter valid Operator ID and PIN number as requested by the SCADAlarm TUI

o Upon authentication Operator should be logged in to the SCADAlarm application
6. Press “0” key from telephone to logout from SCADAlarm
o The confirmation message will be played
7. Press “9” key for exiting the application without acknowledging the alarm
o SCADAlarm will log the information about the operators information, time when Operator logged in and logged out to the system SCADAlarm logger
o Operator will be notified for the current system time and greeted for “Good Bye”
8. Verify the call has been moved on to Third Operator ‘s configured number
o Operator got call on configured number

Specific Post conditions

Second Example:
Add Item to Cart

The actor for this alternative flow is the Authenticated Customer. The flow begins with the user on the Product Description page.
1. The user enters a product quantity to order.
2. The user clicks on the "Add to Cart" button.
3. The system validates the product order information.
4. If the product order information is invalid, the system displays an error message and the use case ends.
If the product order information is valid, the system populates (but does not display) the shopping cart, displays a confirmation message, and the use case ends. The system also populates the Mini Shopping Cart and displays it.



Test Case ID
Test Conditions
Actions to Perform Test
Expected Results
Actual Result
Pass/ Fail
1.
Validation of View Cart Button
1. Authenticated User clicks on “View Cart” button.
· System displays Shopping Cart


2.
Screen validation Shopping Cart Window
1. Check for the following attributes in the above mentioned screen
o Aesthetic conditions
o Validation conditions
o Navigation conditions
o Usability conditions
o Data Integrity conditions
o Specific field test
mentioned in the appendix as applicable
· All applicable parameters mentioned in appendix should be verified.


3.
Validation For Add Item to Cart
1. On the Product Description Page the authenticated user enters the quantity to order.
2.Click on “Add to Cart” button.
· The quantity entered should be displayed. The product order information is validated



4.
Validation For Add Item to Cart

· If the Product Order Information is invalid the system displays an error and a message box stating the same should pop up.


5.
Validation For Add Item to Cart

· If the product order information is valid then shopping cart should be populated and a confirmation message stating the same should be displayed.
· A Mini Shopping cart should be displayed after the confirmation.