SAMPLE TEST PLAN

1. TEST PLAN IDENTIFIER_IPFE.DR-DTPv.1.0_15_5_2011

2. 2.References

o CPE471 Specification
o Lab Statement
o User Guide
o Programmer Guide
o M68K specs
o Test Plan class notes

2. 3. INTRODUCTION
This is the Draft Test Plan for the IP forwarding Engine with direct reference project.
This plan will address only those issues
1. To find the outgoing port number of a given IP address.
2. To ensure that the project perform its aim correctly.
And elements related to object code execution.
The primary focus of this plan is to ensure that the IPFE.DR provides the expected result that
refers to the next port in the network.
The project will have three levels of testing, Unit, System/Integration and Acceptance.
The details for each level are addressed in the approach section and will be further
defined in section eight.
The estimated time line for this project is very aggressive (six weeks).

2. 4. TEST ITEMS

1. Visual studio2008.
The application that used to Test the Program is visual studio2008 tools that
provides a debugging environment to debug and test the code very
accurately for each individual component and to perform the unit test.

2. Hand assembly using paper and pin to verify the work.

2. 5. SOFTWARE & HARDWARE RISK ISSUES

No Problems in software but in hardware we notice that the performance of the

program will go down about 50% or less of its real performance if we don’t use
processor with 3.GH Dual processor and at least 2Gbytes of RAMs.

2. 6. FEATURES TO BE TESTED

 Ensure that the K_value which define the prefix length within the limited range.
 Empty input File.
 Invalid Character in the given input file.
 Invalid Port Number out of (0-2^16).
 Invalid Prefix that is the given prefix not in the range (0-2^K).
 Invalid IP address out the range($0000-0000 __$ FFFF-FFFF)
 Invalid Significant Mask out the range (8-24) bits.

2. 7. FEATURES NOT TO BE TESTED

The Simulation Part of the program (In Future).

2. 8. TEST DELIVERABLES

The testing for the Simulator project will be conducted of Unit, Integration, System and
Acceptance test levels.

 UNIT Testing

Check input file: check if the input file in a valid format or not.

Case 1: valid input file.

Test case Test Input Expected Error Corrective action
specifications Output Log
Valid Fill the input Valid Valid No error ---
input file table with Routing input file Valid
valid routing Table input file
table

Open the
input file and
check for
error

Check if error
was found.
Case 2: invalid character within input file.
Test case Test Input Expected Error Log Corrective
specifications Output action
100728832
invalid Enter 16 1 List of Error line [1] The user

character routing table error will this line has to

100w94368
22 1
input file that 100859904 have includes….etc correct
contains 18 1 element (Like in the the error
100925440
invalid char 16 1 that run window manually
(not decimal 100990976 indicates shown
19 1
digit). 10118s584 to the above.)
20 1 invalid
101253120
Open the 20 1 char.s.
input file and
check for
error

Check if error
was found.
Case 3: out range IP address.
Test case Test Input Expected Error Log Corrective
specifications Output action
5294967295
out Enter 16 1 List of Error line [0] The user

range IP routing table error will the IP has to

input file that have address….etc correct
address
contains out element (Like in the the error
of range IP that run window manually
address out indicates shown
(0000.0000- to out above.)
$FFFF.FFFF) of range
IP
Open the address.
input file and
check for
error

Check if error
was found.
Case 4: out range Port number.
Test case Test Input Expecte Error Corrective
specifications d Output Log action
100859904 18
out Enter 66666 List of Error The user

range routing table 100925440 16 1 error line [0] has to

100990976 19 1
input file that will have the IP correct
Port 101187584 20 1
contains out 101253120 20 1 element Port the error
number of range Port that number manually
number out indicates ….etc
(0-2^16) to out of (Like in
range the run
Open the port window
input file and number. shown
check for above.)
error

Check if error
was found.
Case 5: invalid Mask.
Test case Test Input Expecte Error Corrective
specifications d Output Log action
50331648 8 1
Invalid Enter 100728832 16 1 List of Error The user

Mask routing table 100794368 13 1 error line [5] has to

100859904 18 1
input file that 100925440 16 1 will have Mask correct
contains 100990976 7 1 element value… the error
invalid mask that .etc manually
bit out of indicates (Like in and at
(8-31) to out of the run least put
range window the
Open the Mask shown minimum
input file and number. above.) value.
check for
error

Check if error
was found.
Case 6: validate indexing and subtables:
The run windows above shows when you create the right sub tables and you try
to display any one it will be shown in the right side list box , after checking that
the input file is valid and now what if the k value , prefix one’s count are
invalid?

o Invalid K_value :( 0-7)

o Invalid Prefix: (0-2^k -1)
o Invalid One’s count : (0-8)
Test case Test Input Expected Error Corrective action
specifications Output Log
K_value We force k to 11 Error in Error in The user should
be out of list of the correct the error
range error k_value
:k_value
in range
(0-7)
Invalid We entered With k error in The The user should
Prefix invalid prefix value = prefix in prefix correct the error
2 bit the list should
max of error be in
prefix = range
3 we (0-2^k-
entered 1)
5
Invalid We entered Enter Error in Invalid The user should
one’s invalid one’s list of number correct the error
count number of count = errors of one’s
one’s more 9 indicates : number
than 8 invalid of one’s
number should
of one’s be (0-8)
 INTEGRATION Testing
1. Fine Run
 2. Incorrect input file:
Empty file

3. All Errors:
Input file :
5033d648 8 1

5294967295 16 1

100990976 7 1

100w94368 22 1

100859904 18 66666

100859904 18 -1

10118s584 20 1

List of Errors:
 SYSTEM Testing
After checking errors the Final system now ready and guarantees to any IP
outgoing Port number within 00.00.00 – 00.00.00.001 seconds.

Find Port Part:

Simulation part:

2. 9. RESPONSIBILITIES

Done By Areej Odaat.

3. 10. SCHEDULE
 T1: Writing the first draft of UG and PG and paper.

T2: starting design, suggest algorithm and possible errors and 2nd UD and PG.

T3: start coding for the 1st and 2nd’level indexing, and final Paper draft.

T4: continue coding to find the final result (port number) and first test plan.

T4: Final copy of the software and final UG & PG .also final Paper and test
plan and finish the simulation and experience part.

Activity Duration Dependences

T1 1-week
T2 1-week T1
T3 1-week T1,T2
T4 2-weeks T1,T2,T3
T5 1-week

Activity 18 April - 25 April 2 May - 8 9 May - 15 May 23 May -

24 April - 1 May May 29 May

T1
T2
T3
T4
T5