Home
Project Members
Project Schedule
Project Requirements
Project Progression
Project Report
Analysis
Design
Development
Testing >>

Software Testing

Objectives


1.To ensure that software satisfies requirements in the system requirement specifications.
2.To uncover as many errors as possible in the POSystem to facilitate immediate corrections.
3.To ensure that software is reliable and functional.

Test Schedule 

Date : 11-9-2002  
Venue : Software Engineering Lab  
In-charge : Project Manager | Test Engineers | Chief Programmers
Test Approach
Test Technique

Walkthrough and Inspection
Details
 Persons involved
Project Managers – Jonanthan Pang

Test engineers – Lim Hui San

Programmers – Eunice, Mervin

Meeting duration – 2 hours

Checklist
Errors in declaration 
Errors in control flow 
Computation errors 
Login error 
Interface errors

Test Approach

 White-Box Testing : Procedural testing,Structural testing

Black Box Testing : Stress Testing

Constraints
 Timing constraints
Methods of Testing
 
Customer requirements
 1.User is able to login (Cashier, Managers and System Admin)
 2.Menu shows products to be sold
 3.Software should be able to produce various results
 4.Able to add new products on the menu
Test Cases
 
 1. Authorisation
 ·System should be able to accept different logins by cashiers, 
  managers and system administrator.
 ·Display of menu to user
2. Product Management
 ·Different items shown
 ·Different quantities of products shown
 3. Sales Management
 ·Total sales for a particular cashier
 ·Total sales for that register on that particular day
 4. Printing
 ·Printing of receipt
 ·Printing of total transaction records

View the flowgraph notations and nodes representation of the white box testing technique.

 

Test Results
test cases
expected results
Results obtained
observations if any
User Login as Cashier Valid login-proceed to menu screen User able to log in to interactive screen NIL
User login invalid password format Invalid login-User prompted to re-login User prompted to login again NIL
User login invalid password Invalid login - User prompted to re-login User prompted to login again NIL
User takes order User able to take orders User able to take orders by adding items NIL
User totals amount to be received
Total amount tallied
 Total amout calculated by clicking NIL
User tries to change transactions
Orders can be changed
 Orders can be changed after calculating amount by clicking on modify transaction button User can modify the transaction unlimited times
User calculates amount of change to be given
Accurate change given calculated w.r.t amount given
 Amount of change for amount received from customer is calculated correctly NIL
User prints receipt

Receipt prompt pops up- Receipt printed

 Able to generate unique receipt number and print it Unable to generate continuous invoice number after log out
User logins as manager
Manager logins in
 Manager logs in
 NIL
Manager totals daily transactions
Total sales transaction calculated
 Total sales for that particular register to be printed out
 Simulated total sale transactions to be shown printed out
System Admin logins
System admin logins in
 System admin logs in
 Nil
 
The test engineers also did a stress test by slowly adding 
in the possible situations inordering procedure so that 
the system can be pushed to the limits and performance of 
the system can be gauged.

Cashier logs in
Order taken
Total amount calculated
Transaction to be modified
Order taken again
Amount received is less than total cost
Change calculated
Receipt printed
Modify transactions again
Transactions cleared
User logs out
Manager logs in
Total Sale transaction to be printed out

 
1 1
Hosted by www.Geocities.ws