You are on page 1of 10

QA Testing

Test Case Design Methods
Assignment 1

A. Use case based test case design exercise

You are required to study the application description and the associated use case description given
below to

1. Identify the use paths
2. Prepare test cases to execute all use case paths
3. Prepare additional test cases for data validation
4. Document test suite and test case descriptions

Book point Sales System – Book Availability Inquiry and Supply of Books for Approval to Purchase:

Book point receives inquiries from libraries, companies and individuals regarding availability of books.
Libraries and companies generally inquire about books on various subjects of various publishers and / or
various books published by an author. Some times they inquire about a specific title also.

In the current manual system the manager/clerk searches book catalogs of various publishers on the
subjects. He prepares a list of books on the subject(s). He verifies the stock register and the book-racks to
check availability of the book in the books stores. He verifies which books can be obtained from
publishers or their agents. He intimates the list of books available to the customer.

He prepares a proforma invoice, if the customer is interested in obtaining the books, on approval basis for
purchase. The invoice contains information on books that can be arranged from within the store, and those
need to be procured from publishers or their agents against firm order. As per the profoma invoice books
are collected and packed. Books being supplied on approval basis are recorded in the stock register. The
proforma invoice and the packaged books are sent to the library/company on approval basis for selection
and decision on purchase of books.

The Book Point bookstore intends to automate the book inquiry operation by means of a web based
application. As part of the system analysis the book enquiry operation has been documented as per the
following use case.

Use case Name: Book Purchase Inquiry

Description: Provide necessary information related to books on various subjects. Generate list
of books available on given title, subject, authorize and publisher. Generate and
print proforma invoice for supply of books for approval to purchase, if required.

Actors: Manger, Clerk

Initiation: This use case is executed when the book availability and purchase inquiry from
to customers (libraries, companies and individuals) is received by the
manager/clerk of the bookstore.

Precondition: Stock register and publisher catalog should be up to date.
Use Case Events:

Main Flow:

1. This use case execution begins when actor (clerk/ manager) visits the book point website.
2. System presents the Home Page
3. Actor clicks the Book Point Employee Menu option.
4. System presents a login-in page.
5. Actor logs-in by providing login information.
6. System registers the user and displays bookstore operations menu.
7. Actor clicks the book inquiry menu option.
8. System displays the book inquiry selection menu page containing search options and an option to
return to Home Page.
9. Actor selects one of the search options (by author, by subject, by title) provided.
10. System displays a form to enter search information (author name/subject name /title) and an option to
return to Home Page.
11. User enters the <author name> or <subject name> or <title> and presses submit button.
12. System searches publisher catalogs and stock register and prepares list of books.
13. System displays list of available books. Actor can provide the required information to the customer.
14. System also displays a menu bar containing an option to prepare proforma invoice to supply books on
approval basis and another option to return to Home Page.
15. If the actor selects the prepare proforma invoice option then alternate flow 1 is executed.
16. If the actor selects return to Home Page option at any stage, the Book Point Home Page is displayed.

Alternate Flow 1:

1. Alternate flow 1 is initiated when actor clicks the proforma invoice option on the menu bar.
2. System would display proforma invoice page with options for 1. Show proforma invoice 2. Print
proforma invoice 3. Return to Home Page.
3. Actor selects show proforma invoice
4. System generates proforma invoice.
5. System displays proforma invoice and an OK button
6. Actor clicks OK button
7. System displays proforma invoice page.
8. Actor clicks print option
9. System generates print invoice and prints it
10. Actor clicks return to Home Page option.
11. System displays Book Point Home Page.

Out put:

1. List of books
2. Proforma invoice – printed

Special Requirements:

Label Data Type Presentation Required Validation Rule
User Id String Text Box Yes Ensure User Id is 6 character text
Password String Text Box Yes Ensure password is 6 character
text
Author name String Text Box Yes Ensure text is present
Subject Name String Text Box Yes Ensure text is present
Title Sting Text Box Yes Ensure text is present

Post Conditions: None
A. User Interface Based Test Case Design

Study the user interface of MS Word software. Study the File, Edit, Insert, Format and Table Menu options
and associated user interface flow paths.

Develop test case design for the following usage scenarios:

1. Create a new text file, while doing so, use multiple insert options and format menu options.
2. Edit an existing text file, while doing so use multiple edit, insert and format menu options.
3. Create a new text file containing a table, while doing so use multiple insert and format menu options.

Develop test cases to test the word processor at boundary values. For each usage scenario given above
develop atleast 3-5 tests.

B. Functional Specification Based Test Case Design

Study the functional design specification for the golf score software given below and develop suitable test
case design. You need to develop and document test cases for

a. Functional test
b. Data validation test (including boundary values)

Note: You need to apply equivalence partitioning and boundary value analysis techniques for test case
design

Golfscore Software System:

Golfscore is a program that calculates the scores of the participants in a golf tournament based on the
following assumptions and scoring rules:

Assumptions:

1. The number of courses played can be from 1 to 8.
2. The number of participating golfers can be from 2 to 400.
3. Each golf player plays each course once
4. A golfers tournament score is the sum of his/her score on each course
5. Each golf course has 18 holes and par for each hole is 3,4,or 5

Par: The number of strokes established as a skillful score for any given hole or for a whole course. For
instance the number of strokes established for a hole could be 3 or 4 or 5. A player may put the ball in a
hole Over par (means he has taken more strokes than the set target) or Par (means he has taken just the
target number of strokes only) or 1 under par ( means he has taken 1 stroke less than the target number of
strokes) and so on.

Scoring rules for each role:

Stroke Score

Over par 0
Par 1
I under par 2
2 Under par 4
>2 under par` 6
Input

Input to GOLFSCORE is a formatted text file containing the following records, in sequence:

1. Course records: One record for each golf course. Each record contains the name of the course and the
par each of its 18 holes.
Column 1: Blank
Column 2: Course name
Column 21-38: par for holes 1-18 (par is on integer 3,4 or 5)

2. Delimiter record: Denotes the end of the course records
Column 1: Non-blank
Column2-60: Blank

3. Golfer records: One record per golfer per course (in any order). Each record contains the name of the
course and the actual number of strokes taken for each of the 18 holes.
Column1: Blank
Column2-19: Course name
Column 22-39: Golfer Name
Column 41-58: Number of strokes takes for holes 1-18 (per hole, number of strokes is a single, non
zero digit)

4. Delimiter record: Denotes the end of golfer records.
Column1: Non-blank
Column2-60: Blank

Output

GOLFSCORE produces the following output reports, showing:

1 The name of the golfers, their scores for each course, their total scores, and their final rank in the
tournament, sorted in descending order of total score.
2 The same as report (1), but sorted alphabetically by golfer name
3 Per course, the same as report (1) but sorted in descending order of score on that course.

Each report contains one output record per golfer.
QA Testing
Testing and Test Evaluation
Assignment 2

1. Study test case design document developed in assignment 1 for testing MS Word processor and do the
following.
a. Execute the tests and record results
b. Get your test results evaluated by peer and obtain test evaluation report from him
c. Prepare test evaluation report for your peer

2. Study the test case design document of the client project assigned to you. Also study the test result
documents (defect reports, test case forms) and the test evaluation forms. Interact with the testing team
members to understand how test evaluation activity is carried out.
QA Testing
Testing User Manuals and Documentation
Assignment 3

1. Study the user documentation of MS Excel for the following and test them:

a. Working with work books and worksheets
b. Formatting worksheets
c. Creating formulas and auditing workbooks.

Execute the user documentation steps described under HELP menu in MS Excel for the items cited and
record the test results (defects found, if any).
QA Testing
Software Testing Tools
Assignment 4

1. Study the features of a capture/playback testing tools (such as Win Runner, Silk Test, X Runner) and
prepare a short technical note on its features.

2. Study the automated testing mechanisms being used in the real life client project assigned to you.
Interact with the project ream members to understand how tests are automated. Study few test scripts
for automating testing.
QA Testing
Defect Reporting and Tracking
Assignment 5

1. Study the defect reports assigned to you. Find ways by which clarity in the defect report can be
Improved. Verify whether the defect can be actually reproduced (if access is provided to the
software system).

2. Study defect log and / or defect-tracking tool being used by the testing project assigned to you.
Interact with the testing project team members to understand how defects are logged and tracked
to closure.
Q A Testing
Test Metrics Analysis
Assignment 6

1. Study the test metrics data of the testing project assigned to collect the following information.

a. Number of tests planned, conducted and blocked (build wise)
b. Testing effort (build wise)
c. Defects – found, open, closed, rejected (build wise),
d. Defect distribution - category (root cause) wise, severity wise, functionality wise
e. Days to correct defects (time elapsed between reporting to closure of the defect)
f. Test productivity information – test case design, testing (for each build)

Analyze test information and develop charts for the following

a. Open defects Vs build (or time)
b. Closed defects Vs build (or time)
c. Cumulative open defects Vs time
d. Cumulative closed defects Vs time
e. Defect detection rate (defects found /testing effort) Vs time (weekly)
f. Defect resolutions rate (defects closed per week) Vs time
g. Cumulative defects found over time Vs time
h. Defect distributions root cause wise
i. Defects found functionality wise
j. Testing productivity build wise