Test Documentation

Tutorial 7

September 20

2013
RMIT SOFTWARE TESTING

Question1: Using the format shown below for the test case, prepare the test cases and procedure/script from the given below requirement(s). (Please note: This is a customised/tabular version of the IEEE829 test documentation. For reference to IEEE829 documentation, please see Appendix A. However, these standards are a guideline and it will be customised in the real-word to ensure they are fit-for-purpose.) Business Requirement Case 1: Login page consists of two fields: Username and password. Upon filling the two fields, the user clicks on the Log-in button to see the Welcome Page. The password field should display encrypted format of the test types as (*). If the username is not entered correctly, then the error message should be displayed to the user as Please Enter Valid Username." If the password is not correct, then the error message should be displayed to the user as Please Enter Correct Password." If the user does not remember the password then s/he can click on the Forgot Password hyperlink. The user will be directed to the Forgot Password link page. If the user wants to register, user can click on the Registration hyperlink. The user will be directed to the User Registration page.

TEST CASE
Test Case Test case Objective Steps to Execute Test Data / Input Pass/Fail Expected Result

TEST PROCEDURE Unique-test-procedure: Title

Purpose: Short sentence or two about the aspect of the system is being tested. Test Priority Prereq: Assumptions that must be met before the test case(s) can be run. E.g., logged in, guest login allowed, user testuser exists. Test Data: List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combination of values. These values are written in set notation, one per line. E.g.: loginID = {Valid loginID, invalid loginID, valid email, 2|Page

invalid email, empty} password = {valid, invalid, empty} Steps: Steps to carry out the test. Steps Expected Results Actual Results Pass/Fail

Notes and Questions: Defect Number Cross-reference

NOTE QUESTION Business rule

Question 2: The following business rule has been added to the original requirement. Prepare test design and test cases for the Log-in functionality. Business Requirement Case 1.1:

Username must be greater than equal to 3 characters and Password on login page must be greater than

6 and less than 10 characters

TEST DESIGN

Test case name

Test case# Value

Expected

Test Type

3|Page

APPENDIX A - IEEE 829 TEST DOCUMENTATION

4|Page

5|Page

6|Page