Test Plan Updated

Product Loan Management System (LMS)Version 2.1.04Location http://www.qa-hitekschool.com/lms/loans/2104Author of document Nauman Mithani

: Test Plan: Loan Management System

TABLE OF CONTENTS

(1) REVISION HISTORY OF TEST PLAN.....................................................2

(2) DOCUMENTATION (SUPPORTING).......................................................3

(3) INTRODUCTION.............................................................................4(3.1) Functional Overview (Description of product)...............................5(3.2) Major part (current release specifics)...........................................5(3.3) Risks..........................................................................................6(3.4) Test schedule.............................................................................7(3.5) Resource Estimates (of personnel)...............................................9(3.6) Test Strategy............................................................................10

3.6.1 Smoke Test...............................................................................................103.6.2 Function Test............................................................................................103.6.3 System Test..............................................................................................103.6.4 Bugs reporting..........................................................................................113.6.5 Entry Criteria for Test Execution...............................................................113.6.6 Exit Criteria for Test Execution.................................................................12

(3.7) Tools........................................................................................12(3.8) Environment Requirements.......................................................13

(4) TEST COVERAGE (OUTLINE)...........................................................14(section 1) Areas of Independent Testing............................................14(section 2) Objects and respective Properties.....................................17(section 3) Methods...........................................................................19

(5) TEST CASES..............................................................................26

(1) REVISION HISTORY OF TEST PLAN

Date Author Version of Description

Nauman MithaniHitek CF109

2


document

2013-02-12 Nauman Mithani 1.0 First Draft

2013-04-02 Nauman Mithani 1.1 - “Test Coverage”

section has been

elaborated (and

moved to a new

section).

- “Test Schedule”

has been updated.

- Test Cases section

has been moved to

a new section.

‘

(2) DOCUMENTATION (SUPPORTING)

Software Requirements Specification for the Loan Management System web-

based application is available here:

http://hitekschool.com/file.php/17/Lesson_3/WebLoanAppFunctionalDesign.doc

Internal Design Specification for the Loan Management System web-based

application is available here:


3

http://hitekschool.com/file.php/17/Lesson_3/WebLoanAppFunctionalDesign.doc


http://hitekschool.com/file.php/17/Lesson_3/WebLoanAppInternalDesign.doc

This particular document shall provide the course of action or framework for the

comprehensive testing of the Loan Management System web-based application.

Test cases shall be created and executed towards the smoke, functionality, system and

regression testing.

(3) INTRODUCTION

(3.1) Functional Overview (Description of product)

Its official descriptions are as follows:

Software Requirements Specification: “Loan Prequalifier consolidates many different

functions of loan management processes into a single integrated solution.”

Internal Design Specification: “The purpose of the LMS application is to gather all

customer information and requests in the centralized database.”


4

http://hitekschool.com/file.php/17/Lesson_3/WebLoanAppInternalDesign.doc


The Loan Management System (LMS) is a web-based application used to store customer

financial information with the objective of determination of (1) eligibility of loan pre-

qualification, (2) monetary amount of loan in case of successful pre-qualification.

The LMS also stores information regarding multiple users who have access to it.

(3.2) Major part (current release specifics)

The current version under test is 2.1.04.

No particular official version-specific notes were released. New features are not

expected.

Nevertheless, LMS shall be subjected to smoke, functionality, system and especially,

regression testing.

The functionality testing shall be conducted against both, the Software Requirement

Specification and by ad-hoc.

(3.3) Risks

The LMS application is supposed to be compatible with the Opera web-browser but due to

constraints of time, it could not be tested with Opera; therefore, there may unidentified

compatibility issues.

Secondly, the LMS is also supposed to be compatible with web-browsers run on the Linux

operating system. However, due to the non-availability of the Linux OS, the LMS could not

be tested under Linux; therefore, there may unidentified compatibility issues.


5


(3.4) Test schedule

The total number of potential test cases, across all windows and pages of LMS, has been

counted to be 143.

This includes all

edit fields

list boxes

check boxes

radio list buttons

menu items

hyperlinks and command buttons…

… from the following pages/windows

Log in page = 4

Home page (incl. search results) =

13

Users page = 11

Add User page = 18


6


Edit User page = 18

Customers page = 11

Add Customer page (incl. windows or message or dialogue boxes contained within) =

35

Edit Customer page (incl. windows or message or dialogue boxes contained within) =

33

1) Total number of test cases : 143

2) Timeframe to write average test case : 0.1 hrs. (6 min.)

3) Time to Write Test Cases = 0.1 hrs. × 143= 14.30

hrs.

4) Timeframe for requirements and design analysis = 10% of line 3 =

1.43 hrs.

5) Timeframe for writing Test Plan = 10% of line 3 = 1.43

hrs.

6) Timeframe for creating other test planning materials = 10% of line 3 =

1.43 hrs.

7) Total Test Planning Time = Σ(lines 3 to 6) = 18.59

hrs.

8) Number of builds : 8

9) Number of bugs expected

(average of number of bugs found in previous builds): 20

10)Timeframe to execute average test case : 0.10 hrs. (6 min.)

11)Timeframe for average bug report submission : 0.17 hrs. (10 min.)

12)Timeframe to execute Test Cases = line 1 × line 10 × line 8

= 114.40 hrs.


7


13)Timeframe to report + verify bug fixes = 2 × (line 11 × line 9) = 6.80

hrs.

14)Total timeframe for other test phases

(no knowledge of other phases of testing at this time ∴) 0% of (lines 12+13) =

0.00 hrs.

15)Total Test Execution Time = Σ(lines 12 to 14)

= 120.80 hrs.

16)Total Testing Time = line 7 + line 15 =

139.39 hrs.

17)Number of hours in a day available for testing ≈ 6 hrs./day

18)∴ Timeframe for Total Testing (rounded-up) = line 16 / line 17 ≈

24 business days

System familiarisation: 02/04 – 04/04/2013

Functional Test: 05/04 – 18/04/2013

System Test: 19/04 – 03/05/2013

NOTE:The schedule assumes no work shall be done on the weekends.

(3.5) Resource Estimates (of personnel)

1) Total Personnel: 1


8


2) Total Conduct Time: 24 business days

∴ Effective Total Time required for complete testing (incl. weekends) = 3 weeks

(3.6) Test Strategy

The Test Strategy comprises a series of different forms of tests. This series of tests is

intended to comprehensively exercise the LMS.

The principal purpose of the planned tests is to discover the systems limitations and gauge

its full capabilities.

The list of the series of tests planned, accompanied with brief descriptions, is as follows:

3.6.1 Smoke Test

The Smoke Test shall be the first test performed on each new build to determine its stability

for further testing.

3.6.2 Function Test

The functionality of the LMS shall be tested against the Software Requirements

Specification and ad-hoc.


9


3.6.3 System Test

The focus under this form of test is overall behaviour of the LMS as a system.

User scenarios shall be executed on the system.

Screen mapping shall be executed on the system.

Error messages shall also be tested.

Overall, the System Test shall test the LMS as an integrated system.

The LMS shall also be evaluated for satisfaction of the contents of the Software

Requirements Specification.

3.6.4 Bugs reporting

Defect Tracking System employed: Elementool

All bugs shall be reported and tracked through the Elementool defect tracking service at

www.elementool.com.

Priority assignment:

The Developer or the Business Analyst shall determine and assign priority to all reported

bugs.

3.6.5 Entry Criteria for Test Execution

• All Functional Design documents have been signed off

• All Test cases and other test supporting documents have been completed and approved

• All test data requirements have been identified and test data has been mapped to the test

cases

• Test environments have been setup as per the application requirements

• Test management tool has been setup with required accesses to all testers.

3.6.6 Exit Criteria for Test Execution


10

http://www.elementool.com/


• All Test scripts/cases need to be run at least once

• All defects irrespective of the severity have to be reported to the stake holders

• All defects with severity Critical, High, Medium must be fixed and re-tested successfully.

(NOTE: All minor/cosmetic defects can be deferred to be fixed in later stages)

• All defects need to be moved to terminal stages such as Closed, Non-Defect (e.g.

Functioned as designed or Not a bug) and Deferred. No defect may be in any stage

other the terminal stages.

• All regression defects fixed and retested

• Passed to planned ratio of the tests should be at least 95%

• All Functional Design documents have been signed.

(3.7) Tools

• Elementool defect tracking system

(3.8) Environment Requirements

Requirement specifications (as per Internal Design Specification):

o Standard web browser:

Internet Explorer

Firefox

Opera

Google Chrome

o Operating System:

Windows

Mac OS X

Linux


11


o Hardware Specification:

(not specified)

Workstation specifications:

o Standard web browser:

Internet Explorer

Firefox

Google Chrome

Safari

o Operating System:

Mac OS X Mountain Lion (v10.8.2)

Windows 8 (x64)

(4) TEST COVERAGE (OUTLINE)

(section 1) Areas of Independent Testing

1.1 Deployment (can the web-based app be accessed?)


12


1.2 Help

1.3 GUI (correctness of all graphical elements and text captions/labels)

1.3.1 LMS log-in page

1.3.2 Home page

1.3.2.1User search results

1.3.2.2Customer search results

1.3.3 Main Menu

1.3.4 Users directory

1.3.5 Add User page

1.3.6 Edit User page

1.3.7 Add Customer page

1.3.8 Edit Customer page

1.4 About

1.5 Print(ing)

1.6 Software Compatibility

1.6.1 web-browser compatibility

1.6.1.1Internet Explorer

1.6.1.2Google Chrome

1.6.1.3Mozilla Firefox

1.6.1.4Safari

1.6.1.5Opera

1.7 OS Compatibility

1.7.1 Windows


13


1.7.2 Mac OS X

1.7.3 Linux

1.8 Hardware Compatibility

1.9 Undo

1.10 User Documentation

1.11 Search

1.11.1 Search User by Username

1.11.1.1 partial match of existing username

1.11.1.2 exact match of existing username

1.11.1.3 case sensitivity (uppercase/lowercase)

1.11.2 Search Customer by Last Name

1.11.2.1 partial match of existing Last Name

1.11.2.2 exact match of existing Last Name

1.11.2.3 case sensitivity (uppercase/lowercase)

1.12 “Logout” functional link

1.13 “Home” functional link

1.14 Main Menu

1.14.1 ‘Users’ function (button)

1.14.2 ‘Customers’ function (button)

1.14.3 ‘Settings’ function (button)

1.14.4 ‘Policies’ function (button)


14


(section 2) Objects and respective Properties

2.1: User

2.1.1: Username

2.1.2: Password

2.1.3: First Name

2.1.4: Last Name

2.1.5: Company

2.1.6: Phone

2.1.7: E-mail

2.2: Customer

2.2.1: Title (list menu)

2.2.2: First Name

2.2.3: Last Name

2.2.4: City

2.2.5: State/Province

2.2.6: ZIP/Postal Code

2.2.7: Street

2.2.8: Monthly Income

2.2.9: Monthly Debt

2.2.10:Monthly Payments of


15


2.2.10.1: Monthly Income

2.2.10.2: Monthly Debt

2.2.11:Term Years (radio list)

2.2.12:Returned Customer (checkbox)

2.2.13:Rate

2.2.14:Prequalified Principal of



2.2.14.3: Returned Customer (checkbox)

2.2.14.4: Term Years (radio list)

2.2.15:At

2.2.15.1: Returned Customer (checkbox)

2.2.16:‘Prequalification Letter’ window

2.2.17:‘Rates’ window

(section 3) Methods

3.1: ‘Users’ directory page

3.1.1: ‘Add User’ menu item

3.1.1.1: if an existing user is selected

3.1.1.2: if multiple users are selected

3.1.1.3: if no user is selected


16


3.1.2: ‘Edit User’ menu item

3.1.2.1: only 1 user is selected



3.1.3: ‘Delete User’ menu item

3.1.3.1: if only 1 user is selected



3.2: ‘Add User’ page

3.2.1: Save (button)

3.2.1.1: dependant upon validation conditions of...

3.2.1.1.1: Username

3.2.1.1.2: Password

3.2.1.1.3: First Name

3.2.1.1.4: Last Name

3.2.1.1.5: Company

3.2.1.1.6: Phone

3.2.1.1.7: E-mail

3.2.2: Cancel (button)

3.3: ‘Edit User’ page


3.3.1.1: dependant upon validation conditions of...


17


3.3.1.1.1: Username

3.3.1.1.2: Password



3.3.1.1.5: Company

3.3.1.1.6: Phone

3.3.1.1.7: E-mail


3.4: ‘Customers’ directory page

3.4.1: ‘Add Customer’ menu item

3.4.1.1: if an existing customer is selected

3.4.1.2: if multiple customers are selected

3.4.1.3: if no customer is selected

3.4.2: ‘Edit Customer’ menu item




3.4.3: ‘Delete Customer’ menu item




18



3.5: ‘Add Customer’ page


3.5.1.1: dependant upon validation conditions of

3.5.1.1.1: Title



3.5.1.1.4: Street

3.5.1.1.5: City

3.5.1.1.6: State/Province

3.5.1.1.7: ZIP/Postal Code

3.5.1.1.8: Monthly Income

3.5.1.1.9: Monthly Debt


3.5.3: Get Central Bank Rate (button)

3.5.3.1: Monthly Income validation conditions

3.5.3.2: Monthly Debt validation conditions

3.5.3.3: Returned Customer (checkbox) de/selection


19


3.5.4: ‘Rates’ window

3.5.4.1: Ok (button)

3.5.4.2: close (button) as denoted by the x-symbol

3.5.5: Preview Letter (button)

3.5.5.1: enabled if

3.5.5.1.1: Customer Financial Data edit fields are filled

AND

3.5.5.1.2: Loan Terms edit fields are filled

3.5.5.2: disabled if either is not satisfied

3.5.6: ‘Prequalification Letter’ window

3.5.6.1: Close (button)

3.5.6.2: Save (button)

3.5.6.3: Print (button)

3.5.6.4: close (button) as denoted by the x- symbol

3.6: ‘Edit Customer’ page


3.6.1.1: dependant upon validation conditions of

3.6.1.1: Title


20


3.6.1.2: Street

3.6.1.3: City

3.6.1.4: State/Province

3.6.1.5: ZIP/Postal Code




3.6.3: Get Central Bank Rate (button)

3.6.3.1: Monthly Income validation conditions

3.6.3.2: Monthly Debt validation conditions

3.6.3.3: Returned Customer (checkbox) de/selection

3.6.4: ‘Rates’ window

3.6.4.1: Ok (button)


3.6.5: ‘Prequalification Letter’ window

3.6.5.1: Close (button)

3.6.5.2: Save (button)

3.6.5.3: Print (button)



21


3.7: General text manipulation

3.7.1: cut

3.7.2: copy

3.7.3: delete

3.7.4: select

3.7.5: select all

3.7.6: backspace

3.7.7: paste

(5) TEST CASES

Test cases shall be provided separately.

_____________________________________________________________________________________________

_____________________________________________________________________________________________


22

Test Plan Updated

Documents

Transcript of Test Plan Updated