Basic Test Plan For Software

 

0. Revision History

Date	Changes	Editor
12/4/2007	Original	Lance.Roberts
12/11/2007	Added DN items	Lance.Roberts

 

1. Application Information

1.1 Platform

1.2 Application

1.3 Version

 

2. Test Scope

Define the scope and strategy for testing the system at one or more customers. 

2.1 Scope Summary

This release adds new features for discounting and returns. Testing will cover new feature functional requirements, then transition to regression, performance, and configuration to ensure features work properly across PIN pads and the various card processing host communciation equipment

2.2 Hardware Requirements

Baseline OS and Hardware will be used; in this case current production server IBM x206 and the integrated SP743 Terminal/Server platform will be of primary concern. Other hardware platforms will be considered part of regression and configuration testing.

2.3 Software\OS Requirements

Windows XPe will continue to be the OS for the system and no hotfixes, OS patches, or 3rd Party utilities will be installed as a part of this release.

2.4 Peripheral and 3rd Party Hardware Requirements

Several of the Veriphone and Ingenico PIN pad devices currently being offered and existing at previously installed loctions will be tested against the new features.

 

3. Test Entrance/Exit Criteria

3.1 Entrance Criteria

The Entrance Criteria should be fulfilled before System Test can commence. In the event, that any criterion has not been achieved, the System Test may commence if Product Verification and Project Manager are in full agreement that the risk is manageable.

3.1.1 Software release should be 'Code Complete'

3.1.2 Test Plan must be signed off by Project Manager and Product Verification

3.1.3 Test Hardware and environments must be in place and available for use

3.1.4 Specification documents should be up to date

3.2 Exit Criteria

The Exit Crieria must be achieved before the software can be recommended for release to Customer Lab test or Beta test.

3.2.1 No Class 1 DNs shall exist in system

3.2.2 Class 2 DNs should be limited to 3 in number

3.2.3 At least one test location should be up and running for a period of 2 weeks to ensure no memory leaks or progressive issues surface prior to release to Beta/Pilot testing.

3.2.4 Client Test Lab must perform a UAT and sign off on the waiver for release to Pilot.

3.2.5 Working drafts of manual updates should be available for review by internal and Client QA groups

4. Reference Documentation

4.1 Manuals

4.2 Email and Informal Notes

4.3 Test procedures

 

5. Test Locations

5.1 Manual Testing

The following test locations will perform manual, adhoc, and exploratory testing, where applicable

5.1.1    LAB M1

This location will focus on functional testing of the new feature with a focus on card processing and reporting.

5.1.2    LAB M2

This location will focus on regression, adhoc, and configuration testing

5.2 Automation Testing

The following test locations will perform all automation testing, regardless of type.

5.2.1    LAB A1

This location will focus on performing regression testing existing automated test suites.

Upon the completion of regression testing, randomly generated activity test will continue to run around the clock for performance and stability monitoring.

5.2.2    LAB A2

This location will focus on developing and executing automation tests for the new features.

Upon the completion of developing this new suite of tests, they will be executed on LAB A1 to ensure they continue to run properly on a different test fixture.

 

6. Hardware Configurations

6.1 Store Controller Server Hardware

6.1.1 IBM X206

6.1.2 IBM x205

6.1.3 IBM SP743 Terminal/Server

6.1.4 IBM SP563 Terminal

6.2 Peripheral Hardware

6.2.1 Veriphone MX830

6.2.2 Ingenico I7660

 

7. Functional Testing

7.1 Functional test will be conducted by Manual Test team

7.1.1

7.1.2

7.2 Functionality

List specific features under test, or reference test database table/query for deriving selected test cases

7.2.1

7.2.2

 

8. Regression Testing

8.1 Manual Regression Testing

8.1.1

8.2 Automated Regression Testing

8.2.1

9. Performance Testing

9.1 Manual Performance Testing

9.1.1

9.2 Automated Performance Testing

9.2.1

10. Stress Testing ( Load Testing )

Enumerate test suites or cases that focus high volume, preferably with simulateous activity from multiple controllers.

10.1 Manual Stress Testing

10.1.1

10.2 Automated Stress Testing

10.2.1

11. Configuration Testing

Configuration specific testing for devices and options not specifically targeted in functional testing

11.1

 

11.2

 

 

 

xx. Exclusions