Phase#4 Testing
Structure of a SW Test Plan:
oThe testing process.
1- comonent testing:
We WillTest individual program component in isolation
2- system testing:
a: integration testing:(to-down or bottom up)
b: release testing:( Black -box testing)
PSS testing:
oRequirements traceability.
1-test if PSS resolve the conflect by enter conflect schedules or non conflect schedules.
2 test if staff or student enter valid or invalid date & time.
3-test if admin enter correct and incorrect log in .
4-test if staff or student enter the date out of range or between range.
5-test if the search time is fast or slow if alot of person access to PSS.
6-test the sequred whith use by enter alot number of password.
oTested items.
oTesting schedule...
| Test process Description Duration in(Day) Responsibility of |
|
Component testing Test individual program component 15 Developers
|
|
Integration testing Access to the system source code 7 test team
The system is tested as components
Are integrated
|
|
Release testing Test the complete system to be delivered as 4 test team
black-box
|
oTest recording procedures.
oHardware and software requirements.
Like junit sw if we use it
constraints:
1) determent specific person for the testing ...
2) determent specific time for the testing ...
3) should be determent cost for the testing ...
4) test if all staff& student put there schedules in coordinator office or not.
________________________________________________________________________________________________________________________
Test cases :
1-
| Test case name: Read member information. |
|
Description: collect the mmember information and register of the system.
|
| NO |
Test input |
expected output |
| 1 |
project 1 |
accepted , the name is not taken |
| 2 |
NULL |
not accepted , the name of project is neccesary |
| 3 |
project 2 |
not accepted , the name of project is taken |
| 4 |
123project |
notaccepted , the name of project must start with a character . |
2-
| Test case name : Check student ID |
|
Description : verfy the authenticity of the student's ID ( four digits )
|
| NO |
test input |
expected output |
| 1 |
1234 |
accepted |
| 2 |
5544356 |
not accepted , ID not found |
| 3 |
NULL |
not accepted , Id is required |
| 4 |
Ahmad |
not accepted , a number of four digits is axpected |
3-
| Test case name : check student's number |
| Description : checks the number of students in each project , should be less than or equal to 5 |
| NO |
test input |
expected output |
| 1 |
3 |
accepted , in range |
| 2 |
5 |
accepted , in range |
| 3 |
10 |
not accepted , number larger than 5 |
| 4 |
0 |
not accepted , no project without students |
4-
| Test case name : exclusion cheker |
| Description: the student &staff must enter the exclusion time and date |
| NO |
test input |
expected output |
| 1 |
11 |
accepted |
| 2 |
25 |
not accepted , invalid time |
| 3 |
3-9-2007 |
aceept |
| 4 |
4-5-2008 |
not accepted , out of range |
| 5 |
* |
accepted,exit from the system |
5-
| test case name : chek coordinator ID |
| Description:verfy the authenticity of the coordinator ID(four digit's) |
| NO |
test name |
expected output |
| 1 |
2442 |
accepted |
| 2 |
1234 |
not accepted , not in DB |
| 3 |
4564 |
not accepted , student ID |
| 4 |
null |
not accepted ,i d is required |
| 5 |
ali |
not accepted , it must be four digit |
6-
| Test case name : preferences checker |
| Discription : checks validity of preferences of students or staff members in each project , date range (1-2-2007) to (30-6-2007) |
| no |
test name |
expected output |
| 1 |
25-4-2007 |
accepted , available |
| 2 |
2-5-2008 |
not accepted , date out of range |
| 3 |
2-3-2007 |
not accepted , date taken before |
| 4 |
3-3-2007 |
not accepted , date is an exclusion for one of the students or staff members |
| 5 |
12-6-2007 , 25:30 a.m |
not accepted , invalid time entered |
| 6 |
* |
accepted , end of entering |
Choose inputs that force the system to generate all error messages:
1- Occupy all dates and times in date range

2- Choose a preference date within the exclusion set of one of the students or staff members in a project

3- Enter an out of range date

4- Entered a worng formatted date , or other object rather date type

5- Entered a wrong IP number
Comments (0)
You don't have permission to comment on this page.