3.2.6 Testing and Running a Solution
3.2.6 Testing and Running a Solution (2)
Test strategies specify what type of testing should be carried at each stage.
3.2.6 Testing and Running a Solution (3)
- Alpha and beta testing are different to black and white box testing.
- Carried out when software is nearly complete and is being tested as a whole.
- Applies especially to comercial software: developed for external end user.
3.2.6 Testing and Running a Solution (4)
- Acceptance testing is different once again.
- It is designed to demonstrate to the end user that the software works correctly.
- It shows that all desired features have been implemented.
- Takes place after all other development and testing is complete.
- Software is tested against requirements agreed between developers and end user.
- Debugging tools provide facilities for finding and removing bugs (faults) in software.
- Most obvious is translator diagnostics.
- Messages generated by translator whilst it translates source into object code.
- Useful for finding out where there are syntax errors.
- Often include warnings where there might be a logic error.
To find a logic error, it is useful to use breakpoints and stepping.
- Breakpoints are markers added to a line of code requesting that the program stops runnign when it gets there - useful for carrying out variable checks.
- At this point the programmer can make the program run one instruction or step at a time - this is called stepping.
- Dry runs are executing a program by hand.
- You write in the values of the variables and other runtime data on paper.
- This checks its operation and can track down bugs.
3.2.6 Testing and Running a Solution (5)
It is often carried out using a trace table.
- Gives systematic way of recording what happens when sections of codes are executed.
- It has a column for:
- Line of code being executed
- Every variable used
- Recording any values that are output
- It has a column for:
- It is necessary to ensure that the finished program will run smoothly for the end user.
- This is called installing the program on the end user's computer.
- Executable files (.exe) are often the best way to install a program.
- If they aren't available, the source code and translator program must be copied.
- From the programmers computer to the end user's computer
- Sometimes having just the exe code is not enough to allow.
- The end user may not be able to run the program.
- In this case, we need an installation routine.
3.2.6 Testing and Running a Solution (6)
- This is a program that will automate the installation process.
- The installation routine is geenrally delivered with the software.
- The sorts of functions carried out by the routine are:
- Copying the executable program to the correct folder.
- Preparing any data files that are needed by the program.
- Copying any library files that the program uses.
- Making the program easy to access (icons, shortcuts etc.).
- Initially configuring user preference settings (color scheme etc.).
Some languages provide facilities for creating installation routines.