at 768x1024 resolution
|
|
|
|
| best
experienced with at 768x1024 resolution |
|||
Testing is important as it guarantees quality assurance. Our group has used several methods of testing, namely static and dynamic tests. Static tests include desk checking, walkthroughs, inspections and compilation of the source codes (ASP written using Visual Basic). Our group concentrated on dynamic testing, applying both white-box and black-box testing techniques. Please, do feel free to take a look at our testing methodology and results.
Static and Integration Testing
Black Box Testing
It is important to perform testing on our software so as to ensure that the software created meets the requirements of the clients and that there will not be any compromised performances by the software. Hence, in order to test the software, our group has initiated Black Box Testing, which attempts to find the following types of errors:
1. incorrect or missing functions
2. interface errors
3, errors in data structures
4. performance errors
We have performed the black box testing with numerous test cases as documented, and have found out that our software is sound and it meets the requirements of the client in finding the shortest route from one location to another. Below is the black box testing model that we used in the development of our project.
The outputs produced when the inputs are fed into the "black box" are then compared with the expected outputs. When the expected outputs and the actual outputs tally, we pass the black box test phase. The following table shows the test cases used for testing the bus routes and the actual outputs that we get:
| Inputs | Outputs |
| 1. Bus Service 1 (from Gofy Int.) | Stop1: Gofy Int.Stop 2:Pang's Hospital Stop 3: Buckling Finance Stop 4: Opposite National LibraryStop Stop 5: Han's BuildingStop Stop 6: Holy Trinity Church Stop 7: Tampy Int. |
| 2. Bus Service 1 ( from Tampy Int.) |
Stop 1: Tampy Int.Stop |
| 3. Bus Service 2 |
Stop 1: Tampy Int. |
| 4. Bus Service 3 (From Gofy Int.) |
Stop 1: Gofy Int. |
| 5. Bus Service 3 (From Tampy Int.) |
Stop 1: Tampy Int. |
Because our bus services consist of only 3 services, we can list all the cases and test it out. However, our start point and end point consist of numerous combinations and it is not possible to list out all the possible inputs. We select at random a few start points and end points and test to see if we get the expected fastest route. Therefore we produced the following table:
| Start Point | End Point | Step 1 | Step 2 | Step 3 |
| Dunman Secondary School | MRT Station C | Board Bus 2 at Dunman secondary School | Alight at Pearl Harbour | Walk to MRT station C |
| Holy Trinity Church | MRT Station A | Board Bus 1 (tow Tampy Int) at Holy Trinity Church | Alight at Tampy Int | Walk to MRT station A |
| Buckling Finance | MRT Station B | Board Bus 1 (tow Tampy Int.) | Alight at Han's Building | Walk to MRT Station B |
| Frankman Mall | Tampy Int. | Board MRT at MRT station F | Alght at MRT station A | Walk to Tampy Int |
Table 2 shows the test cases that we have used to test the different start points and end points. However, not all possible combinations are tested due to the large database access. These few points can correctly give you the expected results and therefore we can safely assume that all other combinations are correct. Other black box test cases include the input test cases for the MRT routes.