Test Plan Test Plan OutlineOutline

Test Plan Test Plan OutlineOutline

Key Pointsfrom the Narrative

• process is ad hoc• a lot of code reuse• usability is very important• accuracy and interoperability are

problems• testing is not formal at all

– little or no unit testing of reused modules

Suggested Initial Test Plan

1. Items to be Tested2. Pass Fail Criteria3. Responsibilities4. Schedule of Tests and Reviews

Items to be Tested

1. System Requirements– formal technical review consisting of

1. facilitator: another in-house requirements guru

2. author : Sue3. scribe: Zack4. customer rep - sample user or manager

2. System Design– FTR similar to above

• except use a customer with technical knowledge (eg an IT person)

3. Software Design– FTR

• facilitator: in-house designer from another group

• author: Zack or the other Bob• scribe: Tim or John• member: Tim or John

4. All New Code Modules– code walkthroughs– black box testing

5. All Reused Code Modules– black box testing– white box testing for automatic

ordering module

6. User Interface– Usability Testing

7. System– stress testing, functional testing

2. Pass Fail Criteria• System Requirements

• completeness

• System Design• need a checksheet which includes

survey of users' environment

• Software Design• need a checksheet for design metrics

• New Code Modules• need coding guidelines for walkthroughs• black box - simple black box testing

• Reused Modules• white box - 100% basis paths covered• black box - boundary value analysis

• User Interface• meets all usability criteria described in SRS

– be sure to use different browsers

• System Testing• stress testing based on SRS• does the system do each function described in the SRS

4. Schedule for Tests and Reviews

• SRS FTR - end of week 2• System Design FTR - end of week 3• Software Design FTR - end of week 4• Unit Testing - scheduled throughout

coding• Usability Testing - week 7 (1st half)• System Testing - week 7 (2nd half)