3661J,K,L Case study for Practice activities Web viewCase study for Practice activities. ... The date field stores the current system’s date of the server and the status field contains

Gungley Industrial Machines - Heavy Plant Sales System (HPPS)

Case study for Practice activities

Project plan HPPS-PP extract...........................................................................................2

Test plan HPPS-TP...........................................................................................................7

Functional specification overview HPSS-F01................................................................14

Functional specification HPPS-EX1-FS1.......................................................................19

Functional specification HPPS_LX1_FS3.....................................................................22

Test requirement HPSS-S4A-TR1, extract.....................................................................26

Test requirement HPSS-U17A-TR1, extract.................................................................29

Test requirement HPSS-X5A-TR1, extract...................................................................32

Test requirement HPSS-X11A-TR1, extracts................................................................35

Test script HPSS-S4A-TS1............................................................................................38

Test script HPSS-S4A-TS2...........................................................................................39

Test script HPSS-U17A-TS1.........................................................................................40

Test script HPSS-X5A-TS1...........................................................................................42

Result Log HPSS-RL-1..................................................................................................43

Result Log HPSS-RL-2..................................................................................................44

Result sheet HPSS-S4A-RS1..........................................................................................45

Result sheet HPSS-U17A-RS1.......................................................................................46

Result sheet HPSS-UX5A-RS1......................................................................................47

Result sheet HPSS-X10A-RS1.......................................................................................48

Test summary report HPSS-TS1, extract......................................................................49

Test summary report HPSS-TS2, extract......................................................................51

Test summary report HPSS-TS2, extract 1

Project plan HPPS-PP extract

Project details

Name Heavy Plant Sales System

ID: HPSS

Document Ref: HPPS-PP

Start 2 September 2002

End

Estimated Costs $179,000

Owner Graham Gungley, CEO Gungley Industrial Machines

Description The purpose of this project is to develop and implement software, using internet technology to conduct on-line ordering of heavy plant equipment. Customers will be able to use the internet to browse a product list, and then send an order to sales staff. Sales staff then process the order, and contact the customer.

Objectives The developed software will:

(1) Allow customers to view a list of product specifications and create an order for an individual product.

(2) Allow sales staff to view a list of products and edit product details.

(3) Allow sales staff to view a list of customer orders and update order status

Deliverables (1) Software - Centralised database for order and product details

(2) Software - Centralised web site connecting to the database

(3) Software - On-line (internet) product query and ordering facility

(4) Software - Networked product/order query and editing facility

(5) Documentation – Top level design

(6) Documentation – Test Plan, Results and Analysis

(7) Documentation – Functional Specifications

(8)Documentation – User Guide


(9) Documentation – Operators Guide

Project brief

Gungley Industrial Machines sell heavy plant equipment to mining operations and large agricultural companies. Sales staff receive calls from customers requesting information on plant items. Information is faxed, emailed or mailed to the customer who places an order for a plant item. Past experience has demonstrated that potential customers have been lost due to untimely access to information on product specifications.

The decision to develop the Heavy Plant Sales System (HPSS) is based on its ability to retain customers by providing a service for easy access to product information and ordering. The company’s client base includes remote industrial sites, all with internet access, who will readily accept this technology to perform business.

The HPSS will be resident on the corporate web server. Customers access the system through web pages, over the internet. Sales staff access the system using compiled software, over the corporate network. All application software access over the network will be restricted by the systems administration. The system will be able to handling 10 orders per day, with 2000 hits to the product web pages per month. All completed orders will be deleted at the end of the financial year. The system will reside on the database server computer connected to the corporate internet/intranet server. The database server will be a Leviathan PX4800, with twin Pentium 4 2G processors, Raid 5 hard disk arrays of total 600G and 2G RAM.

HPSS will be developed in three separate sub-systems

Order creationA set of web pages to list product details and create an order. The order created is submitted to the corporate web server, which updates the database.

Order processingA compiled stand-alone program accessed by users logged on to the corporate network. Sales staff list all unfilled orders and can update orders status.

Product maintenanceA compiled stand-alone program accessed by users logged on to the corporate network. Sales staff list all plant items and modify product specifications.

Project scope

To be included A home page to provide links to the product listing and the order form.

Corporate web page layout standards.


To be excluded Any security features. Web pages will be accessible to all internet users. Corporate users access programs through access privileges granted by network administrator.

Project constraints

1. Project must be completed and accepted prior to the financial year beginning 1 July 2003.

2. Consultants will not be available beyond February 2003.

3. All payments to be made during the 2002-2003 financial year.

Stakeholder/communications

Graham Grungley, CEO Gungley Industrial Machines

Cheryl Turner, Financial Controller, Gungley Industrial Machines

Sarah Gaskell, Network Administrator, Gungley Industrial Machines

Simon Symes, Project Manager - Software Development, Gungley Industrial Machines

Greg Cummings, Senior Sales Supervisor, Gungley Industrial Machines

Jane London, Team Leader, Consultant

Judy Wong, Analyst/Programmer, Consultant

Nick Curtis, Programmer, Consultant

Carol Graves, Web developer, Consultant

Assumptions

Representative development environment is available to project team at all stages of the project.

Selected software/hardware platform is adequate for system development

Work schedule

Sep Oct Nov Dec Jan

ACTIVITY 02 09 16 23 30 07 14 21 28 04 11 18 25 02 09 16 23 30 06 13

Prepare & review project plan x

Prepare top-level design x

Prepare functional x x


specifications

Prepare test plan x x

Review design & test plan x

Prepare development environment x x

Program network software x x x x

Program web pages x x x

Prepare project documentation x x x

Perform unit test x x x x

Review unit test x x

Perform integrated testing x x

Review integrated testing x

Perform system testing X

Review system testing x

Perform defect correction x

Review defect correction x x

Perform version control x x

Prepare User Guide x x x x

Prepare Operator Guide x x x

Perform acceptancy x x x x


test

Review acceptancy test x x x x

Perform defect correction x x


Test plan HPPS-TP

Cover sheet


ID: HPSS

Document Ref: HPPS-TP

Date

Status Final

Author Judy Wong - Analyst/Programmer, Consultant

Author Signature

Approval (PM) Jane London, Team Leader, Consultant

Approval Signature

Approval (Owner) Simon Symes, Project Manager - Software Development, Gungley Industrial Machines

Approval Signature

1. Introduction

OutlineThis document provides the test plan for the completing of the events for unit, integrated and system testing of the Heavy Plant Sales System (HPSS).

Document structureThis document has the following structure:

Section 2 Test methodology, outlines the testing approach, the constraint on this process, and the dependencies of tasks.

Section 3 Scope – lists inclusions and exclusions

Section 4 Assumptions

Section 5 Test completion, defines criteria for exiting the testing process

Section 6 Risks

Section 7 Roles and responsibilities


Section 8 Summary of test events

Section 9 Work Schedule (Whole Project)

ReferencesHPSS-PP Project Plan

HPSS-FO Functional Specification (Overview)

Functional Specification HPPS-FO1, version 1.0

2. Testing methodology

OverviewThis section discusses the overall methodology taken to implement the testing phase of the project.

1. Unit testing is performed on each software module. Events include logical and user interface tests.

2. System tests cover functionality, usability, security, disaster recovery, performance testing. Testing to be performed in a simulated environment. Automated test software is used to perform performance and stress testing.

3. Integrated testing is performed on the live system

4. Stress tests performance examine degradation for order entry modules at 2000 transactions per hour.

5. Integrated tests are performed incrementally for each module/database interface component. Components are then grouped for testing into the functionally groups: order processing and product maintenance. Functional groups are combined to test the integrated software.

Constraints1. Project must be completed and accepted prior to the financial year beginning 1

July 2003.

2. Consultants will not be available beyond February 2003.

3. All payments to be made during the 2002-2003 financial year.

4. All unit, system and integrated testing, including any regression testing to be complete before the 16 December 2002.

Dependencies

All unit testing of modules included in systems test to be complete and defect free prior to system testing

All unit testing of modules test to be complete and defect free prior to integrated testing


System testing cannot commence until hardware and software are delivered, and installed

3. Test scope

To be includedTests for potential security risk from the internet

To be excluded User acceptancy testing

Network applications access security

Integrated tests not to include the testing of browser software.

Assumptions Selected software/hardware environments are available to project team at

relevant stages of the project.

Selected software/hardware environments is adequate for testing

Team Members will be available during the testing process, as required

5. Test Completion

All result sheets and logs, for every test collected

All test summaries complete

All defects identified and acceptable to user

6. Risks

Unit testing reveals large number of defects, system and integrated testing delayed

Critical defects identified requiring redesign of software specification

Defect modification requirements exceed the time and budget available

7. Roles and Responsibilities

Name Position Responsibility

Graham Grungley

CEO Gungley Industrial Machines Owner

Cheryl Turner Financial Controller, Gungley Industrial Machines

User representative

Sarah Gaskell Network Administrator, Gungley User representative and testing


Industrial Machines

Simon Symes Project Manager - Software Development, Gungley Industrial Machines

User representative

Greg Cummings Senior Sales Supervisor, Gungley Industrial Machines

User representative and testing

Jane London Team Leader, Consultant Project Manager

Judy Wong Analyst/Programmer, Consultant Test analyst, testing and programming

Nick Curtis Programmer, Consultant Application programming and testing

Carol Graves Programmer, Consultant Web development and testing

8. Summary of test events

8.1 Unit tests

Module(s) tested

Test ID Test Type Comment

… … … …

HPSS-LP1 HPSS-U3A White box Check logic for retrieving product details from database

HPSS-MM1 … … …

HPSS-EX1 HPSS-U17A Black Box Test validation routines and error message displays

HPSS-EX1 HPSS-U18A … …

HPSS-EX1 HPSS-U19A … …

HPSS-LP2 … … …

HPSS-EP1 … … …

HPSS-LX1 … … …

HPSS-UX1 HPSS-U58A … …


HPSS-UX1 HPSS-U59A … …

HPSS-UX1 HPSS-U60A User Interface Check screens against style sheets and Functional Spec.

… … … …

8.2 System tests

Module(s) tested


… … … …

HPSS-EX1

HPSS-LX1

HPSS-S4A Functional Order entered on-line and retrieve by network software.

HPSS-LX1- HPSS-S5A Performance Perform queries on maximum orders

HPSS-UX1 HPSS-S6A Stress Automated test software performs high volume order entry

… … … …

… … … …

8.3 Integrated tests

Module(s) tested


… … … …

HPSS-LP1 HPSS-X3A Integrated In

HPSS-LP1 HPSS-X5A Stress & Load Module/database

HPSS-EX1 HPSS-X6A Stress & Load Module/database

HPSS-LP2 HPSS-X7A Stress & Load Module/database

HPSS-EP1 HPSS-X8A Stress & Load Module/database

HPSS-LX1 HPSS-X9A Stress & Load Module/database


HPSS-UX1 HPSS-X10A Stress & Load Module/database

HPSS-LP1

HPPS-LP2

HPSS-EP1

HPSS-MM1

HPSS-X11A Integrated Interoperability of product maintenance modules

HPSS-EX1

HPSS-LX1

HPSS-UX1

HPSS-MM1

HPSS-X12A Integrated Interoperability of order processing modules

HPSS-LP1

HPSS-MM1

HPSS-EX1

HPSS-LP2

HPSS-EP1

HPSS-LX1

HPSS-UX1

HPSS-X13A Integrated Load all components on operational platform

9. Work schedule

Sep Oct Nov Dec Jan

ACTIVITY 02 09 16 23 30 07 14 21 28 04 11 18 25 02 09 16 23 30 06 13

Prepare & review project plan x

Prepare top-level design x

Prepare functional specifications x x

Prepare test plan x x

Review design & test plan x


Prepare development environment x x

Program network software x x x x

Program web pages x x x

Prepare project documentation x x x

Perform unit test x x x x

Review unit test x x

Perform integrated testing x x

Review integrated testing x

Perform system testing x

Review system testing x

Perform defect correction x

Review defect correction x x

Perform version control x x

Prepare User Guide x x x x

Prepare Operator Guide x x x

Perform acceptancy test x x x x

Review acceptancy test x x x x

Perform defect correction x x


Functional specification overview HPSS-F01

Cover sheet


ID: HPSS

Document Ref: HPPS-FO1

Release No: 1.0

Date

Status Final


Author Signature


Approval Signature

Approval (Owner) Graham Grungley, CEO Gungley Industrial Machines

Approval Signature

1. Introduction

1. ObjectivesThe objectives of the Heavy Plant Sales System are to:

Allow customers to view products and create order over the internet

Allow suppliers to update customer orders using a network application

Allow suppliers to maintain a list of products using a network application

2. Module overviewThe Heavy Plant Sales System (HPSS) has three sub-systems (figure 2.1 System Overview). The order entry sub-system allows an internet customer to list available


products and create an order, submitted to a server. The order processing sub-system provides a facility for a network user (supplier) to retrieve a customers order and enter order status. Products list are maintained the product maintenance sub-system.

All data is stored on a server side database HPSS in two tables: products and orders

3661J_R_CaseStudy_fig01.jpgFigure 1: System overview

Showing the relationship between Customer, Create Orders, Maintain orders, Supplier, Maintain Products

Order entryThe customer selects either to list products or enter orders from a menu: module HPSS-MM1, The list product module HPSS-LP1 displays a list of product items. The enter order module HPSS-EX1 displays a screen base form for customer data entry. When the customer submits the form the orders table is updated.

All modules include for client-side and server-side processes developed using HTML, Javascript and VBScript.


3661J_R-CaseStudy_fig02.jpgFigure 2: Order entry data flow

Showing arrow from Customer to (order details) HPSS-EX1 Enter Order, arrow to Orders. From Products arrows to (product details) HPSS-LP1 List Products to (product details_ Customer.

Order processingThe business user accesses customer order with a network based application. Unprocessed orders are displayed by module HPSS-LX1, and the user selects an item. The selected order is displayed in a form by the order edit module HPSS-UX1. The user can change details and then update the orders table.

3661J__CaseStudy_fig03.jpg


Figure 3: Order processing data flow

Showing arrows from Supplier to (order details) HPSS-LX1 List Orders to (order details) Orders to (order details) HPSS_UX1 Update Orders to (order details) Supplier

Product maintenanceThe business user accesses product details with a network based application. Products are displayed by module HPSS-LP2, and the user selects an item. The selected product is displayed in a form by the product edit module HPSS-EP1. The user can change details and then update the product table.

3661J_R_CaseStudy_fig04.jpgFigure 4: Product maintenance data flow

Shows arrows from Supplier (product details) to HPSS-EP1 Edit Production to (product details) Products to (product details) HPSS-LP2 List Products to (product details) Supplier

Appendix 3 – Data dictionary (extracts)

Table Name: Orders

Field Name Type Size Default Validation rules/Comments

ID Long 0 Assigned by RDBS

Product ID Long 0 Required

Name Text 50 Null Required


Email Text 100 Null Required

Date Date Null Assigned by RDBS

Status Text 10 “new” Required


Functional specification HPPS-EX1-FS1

1. Details


ID: HPSS

Document Ref: HPPS-EX1-FS1

Release No: 0.3

Date


Author Signature


Approval Signature

2. Module function

This module:

Displays a data entry form in a client browser.

Validates user input data

Updates server-side database with valid data

3. Module overview

This module is represented as script in two web files. HPPS-EX1-01-3 is a client side file that displays a data entry form, performs data validation and submits valid data to a server side file HPPS-EX1-02-3. The server-side file connects to the HPPS database and adds the form details to the orders table.

4. Data access

Input None

OutputOrder Table, HPSS database


5. External Components

None

6. Screen layouts

Order screen

3661J_R_CaseStudy_fig05.jpgFigure 5: Order screen

Shows Heavy Plant Sales System, Product Order Entry listing Product ID, Name. Email

7. Object description

All field objects conform to the Style sheet for web design (SS-17) and the corporate colours detailed in the Functional Specification – Overview (HPSS-FO1)

Product Id fieldDefault value is null.

Name fieldDefault value is null.

Email fieldDefault value null.

Submit buttonOn click perform


8. Processes

Validate input Use data dictionary rules validation rules to Product ID, Name and Email fields data entry. Validate data in order of form data entry. For each invalid entry display a standard warning screen with the message Invalid <field name>. On exit from warning screen set focus to invalid field and highlight invalid data.

If all data is valid:

Display message “Data has been successfully submitted” using the standard message screen detailed in the Functional Specification – Overview (HPSS-FO1)

Submit data to server side process update table and display

Update tableReceive form Input. Make connection to HPSS database and add form details to the orders table. The id field is automatically generated by the RDMS. The date field stores the current system’s date of the server and the status field contains the text “new”.

9. Error handling

Trap all client side run-time errors and display using the standard error screen detailed in the Functional Specification – Overview (HPSS-FO1)

Trap all server side run-time errors and display using the standard database error screen detailed in the Functional Specification – Overview (HPSS-FO1)


Functional specification HPPS_LX1_FS3

1. Details


ID: HPSS

Document Ref: HPPS-LX1-FS3

Release No: 0.3

Date


Author Signature


Approval Signature

2. Module function

This module:

Allows the user to select orders to view

Displays requested

Updates server-side database with valid data

3. Module overview

This module is represented as script in two web files. HPPS-EX1-01-3 is a client side file that displays a data entry form, performs data validation and submits valid data to a server side file HPPS-EX1-02-3. The server-side file connects to the HPPS database and adds the form details to the orders table.

4. Data access

Input None

OutputOrder Table, HPSS database


5. External Components

None

6. Screen layouts

Order request

3661J_R_CaseStudy_fig06.jpgFigure 6: Order request screen

Shows Select Order, Individual, Range, All with a choice of Cancel or OK

Order list

3661J_R_CaseStudy_fig07.jpgFigure 7: Order list screen


Shows sample of Customer order list for example: ID=7, Plant ID=999999, Name=FirstName LastName, [email protected]. Date=10/10/02, Status= New.

7. Object description

All field objects conform to the Style sheet for web design (SS-17) and the corporate colours detailed in the Functional Specification – Overview (HPSS-FO1)

Product Id fieldDefault value is null.

Name fieldDefault value is null.

Email fieldDefault value null.

Submit buttonOn click perform

8. Processes

Validate input Use data dictionary rules validation rules to Product ID, Name and Email fields data entry. Validate data in order of form data entry. For each invalid entry display a standard warning screen with the message Invalid <field name>. On exit from warning screen set focus to invalid field and highlight invalid data.

If all data is valid:

Display message “Data has been successfully submitted” using the standard message screen detailed in the Functional Specification – Overview (HPSS-FO1)

Submit data to server side process update table and display

Update tableReceive form Input. Make connection to HPSS database and add form details to the orders table. The id field is automatically generated by the RDMS. The date field stores the current system’s date of the server and the status field contains the text “new”.

9. Error handling

Trap all client side run-time errors and display using the standard error screen detailed in the Functional Specification – Overview (HPSS-FO1)


Trap all server side run-time errors and display using the standard database error screen detailed in the Functional Specification – Overview (HPSS-FO1)


Test requirement HPSS-S4A-TR1, extract

Cover sheet

Project Name Heavy Plant Sales System

Project ID: HPSS

Test Type Functional

Test ID HPSS-S4A

Document Ref: HPSS- S4A –TR1

Date

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides test requirements for the system test HPSS-S4A for the Heavy Plant Sales System (HPSS). Testing is performed against the functional specifications HPPS-EX1-FS3 and HPPS-LX1-FS3, and the user requirements stated in the objectives of the project plan HPPS-TP. This test examines the software’s ability to capture customer orders and make them available for processing to sales staff.


Section 2 Acceptance criteria


Section 3 Test environment


Section 5 Test Script

Section 6 Results


HPSS-TP Test Plan

HPPS- S4A -RS1 Result Sheet

HPPS- S4A -TS1 Test Script

HPPS-RL1 Log Sheet

HPSS-FO1 Functional Specification (Overview), version 1

HPPS-EX1-FS3 Functional Specification, version 0.3

HPPS-LX1-FS3 Functional Specification, version 0.3

HPSS-TD-7 Test Data

2. Acceptance criteria

The web based order entry software correctly stores required data in the database

The network based order query software correctly accesses all required data from the database

3. Test environment

GeneralTest to be performed on a simple peer-to-peer network with one computer acting as a internet and database server, the two client computers. The first client computer accesses the servers over the internet. The other client accesses the servers over the internal network. Tests are performed in the software development section.

HardwareServer: Leviathan P3200, 2G, 2G Ram, 100G HDD

Client 1: Pentium 166M, 32M Ram, 2G HDD

Client 2: Pentium 500M, 128M Ram, 20G HDD

Network: 3 x NE2000 comp. NICs, 4 port hub + cables


SoftwareServer: Windows 2000 server, JV Enterprise Internet Server 6.0, QTRAN database server 1.1, the database file HPPS, the web page for module HPPS-EX1 and the executable program for module HPPS-LX1.

Client 1: Windows 98, Internet Explorer 4.0 and Netscape Navigator, configured as a standalone terminal with internet connect over a LAN.

Client 2 Windows 2000 client, configured as a network terminal

Test data Prior to testing the database table Orders is empty.

This test will be conducted with test data is found in the file HPSS-TD-7.txt.

4. Roles and responsibilities


Jane London Team Leader, Consultant Authorising Result

Nick Curtis Programmer, Consultant Testing

Carol Graves Programmer, Consultant Testing

5. Test scripts

This test uses the test scripts HPPS-S4A-TS1 and HPPS-S4A-TS2

HPPS-S4A-TS1 is performed before HPPS-S4A-TS2

6. Results

Test results entered into sheet HPPS- S4A-TS1 by tester

Completed results authorised

Test results to be entered into log HPPS-RL1


Test requirement HPSS-U17A-TR1, extract

Cover sheet


Project ID: HPSS

Test Type Black Box

Test ID HPSS-U17A

Document Ref: HPSS- U17A –TR1

Date

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides test requirements for the unit test HPSS-U17A for the Heavy Plant Sales System (HPSS). Testing is performed against the functional specification (HPPS-EX1-FS3) for the module HPPS-EX1, version 3. This test examines the software’s ability to correctly validate user input.







Section 6 Results


HPSS-PP Test Plan

HPPS-U17A-RS1 Result Sheet

HPPS-U17A-TS1 Test Script

HPPS-RL1 Log Sheet




Validation rules applied, as stated in data dictionary

Correct message displayed in response invalid data entry, as stated in module functional specification

Correct confirmation displayed when valid data is submitted

3. Test environment

GeneralTest to be performed on a simple peer-to-peer network with one computer acting as a internet and database server, the other as a client. The client computer accesses the server over the internet. Tests are performed in the software development section.


Client: Pentium 166M, 32M Ram, 2G HDD


SoftwareServer: Windows 2000 server, JV Enterprise Internet Server 6.0, QTRAN database server 1.1, web page for module HPPS-EX1 and the executable program for module HPPS-LX1

Client: Windows 98, Internet Explorer 4.0 and Netscape Navigator, configured as a standalone terminal with internet connect over a LAN.

Test data No test data is provided for this test






5. Test scripts

This test uses the HPPS- U17A-TS1 test script

6. Results

Test results entered into sheet HPPS-U17A-RS1 by tester

Completed results authorized



Test requirement HPSS-X5A-TR1, extract

Cover sheet


Project ID: HPSS

Test Type Stress and Load

Test ID HPSS-X5A

Document Ref: HPSS-X5A–TR1

Date

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides test requirements for the unit test HPSS-X5A for the Heavy Plant Sales System (HPSS). HPSS-X5A is one of a set of stress and load tests in the range HPSS-X5A to HPSS-13A. This test applies stress to module HPSS-LP1 and the database interface.

The test places a load on the software by accessing and processing 10000 test records from the HPSS database, and recording the response times.







Section 6 Results


HPSS-PP Test Plan

HPPS-X5A-RS1 Result Sheet

HPPS-X5A-TS1 Test Script

HPPS-RL2 Log Sheet


HPSS-X6A-TR1 Test requirements









Module HPPS-LP1 accesses, formats and displays 100,000 records in less than 30 seconds over a simple intranet.

3. Test environment

GeneralTest to be performed on a simple peer-to-peer network with one computer acting as a internet and database server, the other act as clients. The client computer accesses the server over the intranet. Tests are performed in the software development section.


Client: Pentium 166M, 32M Ram, 2G HDD



SoftwareServer: Windows 2000 server, JV Enterprise Internet Server 6.0, QTRAN database server 1.1, web page for module HPPS-EX1 and the executable program for module HPPS-LX1

Client: Windows 98, Internet Explorer 4.0 and Netscape Navigator, configured as a standalone terminal with internet connect over a LAN.

Test data The database table “products” contains 10000 dummy records. Data is generated randomly for each field in this table within the ranges derive from the data dictionary.





5. Test script

This test uses the HPPS- X5A-TS1 test script

6. Results

Test results entered into sheet HPPS-X5A-RS1 by tester




Test requirement HPSS-X11A-TR1, extractsCover Sheet


Project ID: HPSS

Test Type Integrated

Test ID HPSS-X11A

Document Ref: HPSS- X11A –TR1

Date

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides test requirements for the unit test HPSS-X11A for the Heavy Plant Sales System (HPSS). Testing examines the interoperability of the modules HPSS-LP1, HPSS-LP2 and HPSS-EP1, with the database table “products”.







Section 6 Results


HPSS-PP Test Plan

HPPS-X11A-RS1 Result Sheet

HPPS-X11A-TS1 Test Script

HPPS-RL2 Log Sheet


HPPS-LP1-FS3 Functional Specification, version 0.3

HPPS-LP2-FS3 Functional Specification, version 0.3


2. Acceptance Criteria

Web module retrieves product list maintained by network application

3. Test environment

GeneralTest to be performed on a simple peer-to-peer network with three computers. One computer acting as an internet and database server, one as an internet client and the other as an network client The internet client computer accesses the server over the internet. The network client is configured as a network workstation accessing the software locally. Tests are performed in the software development section.


Internet Client: Pentium 166M, 32M Ram, 2G HDD

Network Client: Pentium 500M, 128M Ram, 20G HDD


SoftwareServer: Windows 2000 server, JV Enterprise Internet Server 6.0, QTRAN database server 1.1, the database file HPPS, the web pages for modules HPPS-MM1 and HPPS-EX1, and the executable program for modules HPPS-LP2 and HPPS-EP1.

Internet client: Windows 98, Internet Explorer 4.0 and Netscape Navigator, configured as a standalone terminal with internet connect over a LAN.


Network client: Windows 2000 client configured to log on to server, and run executables modules.

Test data Prior to testing the database table product is empty.

This test will be conducted with test data is found in the file HPSS-TD-11.txt.





5. Test scripts

This test uses the test scripts HPPS-X11A-TS1 and HPPS-X11A-TS2

HPPS-X11A-TS1 is performed before HPPS-X11A-TS2

6. Results

Test results entered into sheet HPPS-X11A-RS1 by tester




Test script HPSS-S4A-TS1Project Name Heavy Plant Sales System

Project ID: HPSS

Test ID HPSS-S4A

Document Ref: HPSS- S4A –TS1

Date

Test purposeTo ensure that a range of valid data can be submitted to the database

Test conditions Module HPSS-EX1 displayed in IE 4.0 browser

Test data stored in HPPS-TD7.txt. Each row represents a record to be entered. Asterisks separate the field data for Product ID, Name and Email.

Test stepsFor each record in turn, perform the following steps:

Left click Product ID field and enter test data

Select Name field and enter test data

Left click Email field and enter test data

Left click Submit button

Left click Ok button

Expected resultsOn completion of each order entered the message ““Data has been successfully submitted” is displayed.


Test script HPSS-S4A-TS2Project Name Heavy Plant Sales System

Project ID: HPSS

Test ID HPSS-S4A

Document Ref: HPSS- S4A –TS2

Date

Test purposeTo ensure that:

Data enter from the Order Entry software has been correctly stored.

Data stored during Order Entry can be retrieved for processing.

Test conditionsModule HPSS-LX1 start-up screen displayed.

No other applications running

Test data stored in HPPS-TD7.txt. Each row represents a record to be entered. Asterisks separate the field data for Product ID, Name and Email.

Test stepsFor each record in turn, perform the following steps:

Left click View menu item

Left click Orders drop down menu item

Left click All radio button


Select Email field and enter test data

Expected resultsOn completion of the steps a screen displays a list of 10 orders. Each order includes the values enter from test data. Records appear in the same order as the test data. Each order has a value in the price field.


Test script HPSS-U17A-TS1Project Name Heavy Plant Sales System

Project ID: HPSS

Test ID HPSS-U17A

Document Ref: HPSS-U17A-TS1

Date 31 July 2002

Test purposeTo ensure that:

The HPSS-EX1 module validates input data

The HPSS-EX1 module submits valid data for database storage

Test conditionsModule HPSS-EX1 displayed in IE 4.0 or Netscape Navigator 4.0 browser

Test stepsPerform the following steps for both browsers:



Select Product ID field and enter ABCD



Select Product ID field and enter 9999

Select Name field and enter 9999



Select Name field and enter Fred Smith


Expected resultsOn completion of the above steps the Order Entry module should display the following messages, when the Submit button is clicked


“Invalid Product Id”

“Invalid Product Id”

“Invalid Name”

“Data has been successfully submitted”

When the Ok button is click the cursor should be placed in the field referred to by the message.


Test script HPSS-X5A-TS1Project Name Heavy Plant Sales System

Project ID: HPSS

Test ID HPSS-X5A

Document Ref: HPSS- X5A –TS1

Date

Test purposeTo ensure that database access and output formatting process are with acceptable

Test conditions Module HPSS-MM1 displayed in IE 4.0 browser

The product table of the HPSS test database has 100,000 records.

Test steps Left click “Display product list” hyperlink in the main menu and start

stopwatch.

When product listing is displayed stop stopwatch

Record stopwatch time

Expected resultsOn completion the first step the product listing should appear within 30 seconds.


Result Log HPSS-RL-1Project Name Heavy Plant Sales System

Project ID: HPSS

Page Number: 1

Document Ref: HPSS-RL1

Date Time Test ID Status Comment

… … … … …

14/10/02 10:30 HPSS-U3A Fail

… … … … …

15/10/02 11:30 HPSS-U17A Fail

… … … … …

05/11/02 15:00 HPSS-U60A Fail

… … … … …

HPSS-X3A Fail

… … … … …

02/12/02 14:30 HPSS-S4A Fail

02/12/02 17:30 HPSS-S5A Incomplete Test platform not available

03/12/02 09:30 HPSS-S6A Pass Alternate software used to perform test

… … … … …

… … … … …

Authorised (Signature)


Result Log HPSS-RL-2Project Name Heavy Plant Sales System

Project ID: HPSS

Page Number: 1

Document Ref: HPSS-RL2

Date Time Test ID Status Comment

… … … … …

11/11/02 9:30 HPSS-X5A Pass

11/11/02 13:30 HPSS-X6A Pass Incorrect screen layout

11/11/02 14:30 HPSS-X7A Pass

13//11/02 10:15 HPSS-X8A Pass

15/11/02 12:15 HPSS-X9A Pass

18/11/02 10:00 HPSS-X10A Fail Database hangs at 500 trans/10 mins.

19/11/02 15:00 HPSS-X11A Fail Web page does not show product price

HPSS-X12A Incomplete Components not available

HPSS-X13A Incomplete Components not available

… … … … …

… … … … …

… … … … …

… … … … …




Result sheet HPSS-S4A-RS1

Test result record


Project ID: HPSS

Test ID HPSS-S4A

Document Ref: HPSS-S4A-RS1

Date

Observed Result When performing the test script HPPS-S4A-TS2 actual results did not match with expected results. The product price is not displayed in any order record displayed.

Error Description No other errors observed

Outcome Fail

Tester (Signature)



Result sheet HPSS-U17A-RS1

Test result record


Project ID: HPSS

Test ID HPSS-U17A

Document Ref: HPSS-U17A-RS1

Date

Observed Result Expected error message not displayed when invalid data entered into name field.

Error Description Module does not identify test data as invalid. Does not match functional specification for this module.

Outcome Fail

Tester (Signature)



Result sheet HPSS-UX5A-RS1

Test result record


Project ID: HPSS

Test ID HPSS-X5A

Document Ref: HPSS-UX5A-RS1

Date

Observed Result

Error Description

Outcome

Tester (Signature)



Result sheet HPSS-X10A-RS1

Test result record


Project ID: HPSS

Test ID HPSS-X10A

Document Ref: HPSS-X10A-RS1

Date

Observed Result Software display error message and hangs when more than 500 orders are processed in a 10 minute period.

Error Description The following message was displayed:

QTRAN database server 1.1

Error 000456 Buffer overflow – Process aborted.

Outcome Fail

Tester (Signature)



Test summary report HPSS-TS1, extract

Cover Sheet


Project ID: HPSS

Document Ref: HPSS-TS1

Date 09 December 2002

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides a summary of the test events detailed in the project test plan (HPSS-TP).


Section 2 Test completeness, examines the overall completion of testing process

Section 3 Problems, identifies any problems encountered during the testing process

Section 4 Results, details defects identified during the testing process.

Section 5 Conclusions, evaluates the severity of identified defects



HPSS-TP Test Plan

Test Requirements for all tests

Test Results for all tests

Test Scripts for all tests

HPSS-RL1 Test Log

2. Test completeness

Test HPSS-S5A was not performed, due to the lack of required number of client terminals with correct specifications. All other test complete.

3. Problems

HPSS-S6A – The automated third-party test software used to perform the test did not give the expected type of results require by the test. Custom-built software developed by project used instead.

4. Results

This section list only those tests which have failed:

1. HPSS-U17A – Error message not displayed when user invalid blank name.

2. HPSS-S4A – Price entered in the web form not displayed in the order query screen of the network software.

3. HPSS-U3A – First product record is not listed; program crashes when accessing an empty database table.

4. HPSS-U60A – Colour matching of screen background incorrect. Font is not consistent with style sheet.

5. HPSS-X3A – Network programs do not run due to missing library components.

6. …

7. …

5. Conclusion


Test summary report HPSS-TS2, extract

Cover Sheet


Project ID: HPSS

Document Ref: HPSS-TS2

Date

Status Final


Author Signature


Approval Signature


Approval Signature

1. Introduction

OverviewThis document provides a summary of the stress and load test events of the integrated platform detailed in the project test plan (HPSS-TP). This summary covers the tests HPSS-X5A to HPSS-X13A.


Section 2 Test completeness, examines the overall completion of testing process

Section 3 Problems, identifies any problems encountered during the testing process

Section 4 Results, details defects identified during the testing process.

Section 5 Conclusions, evaluates the severity of identified defects



HPSS-TP Test Plan

Test Requirements for all tests

Test Results for all tests

Test Scripts for all tests

HPSS-RL1 Test Log

2. Test completeness

Test HPSS-S5A was not performed, due to the lack of required number of client terminals with correct specifications. All other test complete.

3. Problems

HPSS-S6A – The automated third-party test software used to perform the test did not give the expected type of results require by the test. Custom-built software developed by project used instead.

4. Results

This section list only those tests which have failed:

1. HPSS-U17A – Error message not displayed when user invalid blank name.

2. HPSS-S4A – Price entered in the web form not displayed in the order query screen of the network software.

3. HPSS-U3A – First product record is not listed; program crashes when accessing an empty database table.

4. HPSS-U60A – Colour matching of screen background incorrect. Font is not consistent with style sheet.

5. HPSS-X3A – Network programs do not run due to missing library components.

6.

7.

3. Conclusion


Documents

3661J,K,L Case study for Practice activities Web viewCase study for Practice activities. ... The date field stores the current system’s date of the server and the status field contains