1. Test Plan Identifier
New Testing Site

2. Introduction

2.1 Objectives
The new personal website of Ian Worrell is to be tested at the Unit and system levels. Testing will mainly be manual, however automated tools may be used if very cost effective. A variety of test techniques will be utilised. Functional and non-functional testing will be exercised.

The test schedule is extremely constrained by the lack of time resource. Aniticipated completion times are extremely vague. Deliverables and milestones are anticipated to be incremental in nature.

2.2 Test Strategy
Both Unit and System testing will take place. For both elements there will be a "test first" strategy, where the test cases are driven by the user requirements. Thus once an enhancement has been identified that will meet a user need, a requirement will be drawn up, a simple architecture designed, test cases created, a prototype developed, prototyped tested, actual code written, tested and retested and integrated into the rest of the system. Build often, test often.

2.3 Scope
Testing will extend only to the software functionality of the online site and the underlying code. Both functional and non-functional requirements will be tested.

Excluded are the database, development script and business reviewing of the content.

2.4 Reference Material
To be determined

3. Test Items

3.1 Site Modules
A single page is to be considered the smallest possible module. However a group of pages, or indeed a whole site can be considered a module if an enhancement has an impact on that many pages.

3.2 User Procedures
Google and other engines will be searched periodically to ensure that site details are displayed correctly.

4. Features To Be Tested
All new pages; all amendments to an existing page where that impacts on a new page, all new features relating to 3rd parties.

5. Features Not To Be Tested
Any feature that appears solely on an existing website page.

6. Approach
As close as possible to a industry standard level. Thus adherence to standards based vocabulary and techniques, even if this slows up development.

6.1 Component Testing
Component testing will be undertaken for all enhancements. The definition of component used is from the BS7925 glossary. "A component is the lowest level for which a separate specification exists." A number of components may be included in the same test spec. For a description see more

6.2 Integration Testing
Once each individual component has been tested in all environments, it will be combined with other new, amended, and existing unamended components to ensure that they correctly integrate. For a description see more

6.3 Interface Testing
The primary interfaces for testing are with third parties. This will be completed initially within the confines of the home PC, then with test pages and finally the live system.For a description see more

6.4 Security Testing
Virus scans.

7. Item Pass/Fail Criteria
The component or integrated system under test meets a specified requirement to be considered a pass. This includes implicit requirements such as stability.

8. Suspension Criteria And Resumption Requirements
The requirements or developed code are of such poor quality as to be untestable.

8.1 Suspension Criteria
A review process will be undertaken to declare, a document or code is untestable.

8.2 Resumption Criteria
A review process will be undertaken to declare, a document or code is testable.

8.3 Approval Criteria
As the development corporation consists of one individual, a process exists to ensure that many different hats are worn and that acceptable Chinese walls exist.

9. Testing Process
Changes to the site will be "enhancement". For each enhancement a spreadsheet will be drawn up with the requirements on one sheet, and the test spec on another. A third sheet will have the summary.

9.1 Test Deliverables
Test Plan, Test specs, incident log

9.2 Test Responsibilities
All testing to be undertaken by Ian Worrell

9.3 Test Resources
A shoestring.

10.Testing Tasks Remaining
No test tasks should be outstanding at the time of completion of each enhancement.

11.Environmental Needs

11.1 Hardware
No hardware will be required, other than a PC.

11.2 Software
Word and Excel

11.3 Security
Wherever possible the software will be checked for leaks. In particular are user details displayed.

11.4 Tools
If tools can be purchased cheaply or on evaluation this will be facilitated.

11.5 Publications
No documentation will be supplied, other than online documentation.

12.Responsibilities
Ian W is the man.

13.Staffing And Training Needs
No additional test staff are required.

14.Schedule
Personnel involved in testing have to fit their activities in to the rest of their lives. This makes estimating completion dates very difficult. On an individual enhancemnt, the intention is to be accurate to within 1-2 days.

15.Risks And Contingencies

Ian loses interest. - The website left to wither on vine.
Severe data loss. - Data backed up, compiling scripts backed up.
Scope may change - Constant checking for feature creep.
Increase in defects rise dramatically
Late delivery

16.Approvals
Ian Worrell, friends and colleagues.