Home
Project Members
Project Schedule
Project Requirements
Project Request
Project Progression
Project Report
Analysis
Design
Development
Testing »
Project Report - Testing
In order to ensure the software is functioning as what is expected and to meet the customer’s requirements, it is essential to organize a systematic and well-planned testing strategy. Thus we come to this proposed testing strategy, which covers brief information on the testing objective, testing method, and testing schedule.

Objective:

Uncover as many errors as possible on Inventory Database Management System for a Supermarket in minimum amount of time to facilitate immediate correction and to maintain the software reliability and functionality.

Method:

The testing is implemented based on spiral structure and cover 4 types of testing: Unit testing, Integration Testing, Validation Testing, and System Testing. (Please refer to Pressman’s Software Engineering A Practitioner’s Approach pg.461 for details). 

Unit Testing and Integration Testing have been done concurrently with the software developing process by the programmers. Both testing has covered static test of desk checking and compilation checking.

Validation Testing and System Testing are done by the software testing officer, with the cooperation of the software programmers. Black Box Testing Techniques will be used throughout the process due to the time constraints.

Schedule:

1.      Test type:   Validation Testing

      Date     :         Thursday, 14 March 2002     

      Time     :   8:45 – 10:15

      Venue    :  Digital Automation Lab

      Personnel:  Project Manager, Chief Programmer, Testing Officer

 

2.      Test type:   System Testing

      Date     :         Thursday, 21 March 2001     

      Time     :   8:45 – 10:15

      Venue    :  Digital Automation Lab

      Personnel:  Project Manager, Chief Programmer, Testing Officer

 

Validation Test

Objective:

Ensure the software is functioning as close as possible in a manner expected by the client.

Customer requirements:

·         Capability in displaying data, editing data fields

·         Maintenance of database among various databases

·         Prediction of demand for a particular product

·         Visual aid of demand prediction for manager

·         Prompting of date-expiry/out-of-stock

Test Cases:

1. Authorizing sub-system

1.1 Log in

1.2 Display/Edit company’s information

1.3 Add user and edit user’s information

 

2. Database Management Setting Subsystem

2.1 View product list/products in each class

2.2  Add/edit/delete new product class

2.3 Read/update consolidated sales

 

3. Demand prediction sub-system

3.1 View best/worst sales

3.2 Display expired/out-of-stock products

3.3 Display any record by item code

3.4 Draw sales curve for any record

3.5 Generate demand prediction

3.6 Prompt date-expiry/out-of-stock warning

 

4. Printing sub-system

4.1 Print ordering bill

4.2 Print store information

4.3 Print transaction record for both customer and company

Test Code

Expected result

Observed result

Remarks

1.1

Legal user is able to login

Existing user with correct password is able to login

Satisfied

1.2

User is able to view and edit the company’s information

User is able to view and update the company’s information

Satisfied

1.3

User is able to add new users with valid particulars and modify an existing user’s particulars

Any new users can be added even the user name is existing and user’s information can be searched out and modified

Unsatisfied

2.1

User is able to view the product list or view the products that are in one class

All the products can be displayed in a list. Class can be specified but have not seen the products in the class

Satisfied

2.2

User is able to add new product class with valid ClassID and edit/delete existing product class

  The user is able to add/edit/delete product classes.

Satisfied

2.3

User is able to read/update consolidated sales

  Read/Update of consolidated sales is available.

Satisfied

3.1

User is able to see the best/worst sales

  Best sales can be seen. Worst sales not part of requirements and no need to be seen by user.

Satisfied

3.2

User is able to see all the products that are either expired or out-of-stock

  Expired products can be seen.

Satisfied

3.3

Record of any item can be displayed by its item code

Item records can be seen. 

Satisfied

3.4

A proper sales curve is drawn with respect to given record

  Drawing of curve can be done with Access XP edition.

Satisfied

3.5

A reasonable future demand is predicted by the system

  Small bug exist whereby sometimes predicted value is a negative number. Overall no problem.

Satisfied

3.6

If any product is expired or out of stock, the system is able to prompt a proper warning

  User have to select the function to show list of expired product. No automated function.

Satisfied

4.1

Ordering bill can be printed

  Printed.

Satisfied

4.2

Store information can be displayed

  Can be displayed.

Satisfied

4.3

Transaction records for both customer and company can be printed

Printed. 

Satisfied

 

System Test

Objective:              

Promote software functionality, reliability and maintainability 

 

Concept:

Test the software as a whole unit of program, especially in test cases not included in validation test. 

Test Cases:

1.     Software performance in various operating systems

1.1 Running the application in newly developed Windows platforms

1.2 Running the application in Unix/Linux platforms 

1.     Access level validation

2.1 Login as cashier

2.2 Login as store man

2.3 Login as manager

2.     Database maintenance

3.1 Update and backup the database

3.2 Check the reliability of the backup

3.     Networking supporting

Allow different user to access database from different computer via Intranet

4.     Program termination mechanism

5.1 Exit from program normally: use provided exit option.

5.2 Exit from program abnormally: abort in the middle of the program.

5.     User-friendly interface

6.1 Guide on how to use the program and online help

6.2 Information about the developers and software

 

System Test Observation:

Test Code

Expected result

Observed result

Remarks

1.1

Program is executable in newly developed Windows platforms

Program is applicable in Windows 2000/ XP

Satisfied

1.2

Program is executable in Unix/Linux environment

The application is not suitable for Unix/Linux environment

Unsatisfied

2.1

User is able to access cashier interface and not other interfaces

  Cashier only access the switchboard for cashier interface.

Satisfied

2.2

User is able to access storeman interface and not other interfaces

  Storeman only access the switchboard for storeman interface.

Satisfied

2.3

User is able to access manager interface and other interfaces. Warning is prompted if any of product is expired/out-of-date

  Manager only access the switchboard for manager interface.

Satisfied

3.1

Backup of database should be made periodically

  Depends on user. No automated function.

Satisfied

3.2

Backup device is rather safe and independent

  No hardware available for backup.

Unsatisfied

4

Different user is able to access database from different computer via Intranet

  Yes. Can be accessed. (Read only)

Satisfied

5.1

Changes in the program are saved and program terminates

  Yes. Records are saved.

Satisfied

5.2

User is asked for assurance to abort the program and whether user wants to save the design or not.

Yes. Critical commands are confirmed. 

Satisfied

6.1

User-friendly guide on how to use the software and online help should be provided.

Currently unavailable.

Unsatisfied

6.2

Information about the developer and year of production should be available.

Qun Yin Ltd., 2002

Satisfied

 

 

Hosted by www.Geocities.ws

1