- software and test data which run the programming code - under different conditions - monitor output - compared against expected output - report summarised for how well the program behaved and produced accurate results
1 of 19
Performance testing
- Determine how fast some aspect of a system performs under a certain workload - can demonstrate that the system meets performance criteria - compare two systems - can see what parts of the the system/workload caused issues
2 of 19
Scalability testing
- ensuring the system can cope with increases in workload
3 of 19
Volume testing
- ensures that when volumes become larger this can be accommodated by the program - and it will not cause the program to stop or cause poor performance
4 of 19
Usability testing
- test how well people can use an ICT system for its intended purpose
5 of 19
Multi platform testing
- ensure that the solution can work across various different platforms
6 of 19
Portability testing
-ensuring that the solution can be transferred to specified hardware or software.
7 of 19
Prototyping
- producing working versions of the ICT system -at different stages of development - given to user/client - test and evaluate any problems - allows you to match the user's needs better
8 of 19
paper prototyping
- creating a paper based prototype - the user can they try this and see if they like it and are able to use it - any issues or problems are noted down and any additions can be added there and then.
9 of 19
Using a stimulated environmment
- behaving as though it were being used in its actual situation - the correct number of terminals that would be used - also used to see how the system behaves when subjected to a series of controlled inputs.
10 of 19
Module testing
- testing one module at a time - allows tester to focus on just one aspect - this would be signed of by client
11 of 19
Integration testing
- combining modules together and then testing how they work together - this will be signed of by the client
12 of 19
System testing
- testing the system as a whole and how all modules link together
13 of 19
White box
- testing done by people who are familiar with the programming and the programming code
14 of 19
Black box
- done by people who will never look at the programming code - they look at output produced - check that any requirements or specifications have been meet
15 of 19
Alpha
- tests that are done before it's released for public use - usually performed at an in house site not normally involved with systemdevelopers
16 of 19
Beta
- preliminary version of the program that is widely distributed before commercial use - often tested by heavy duty demanding users
17 of 19
Functional
- Type of black box testing that the specifications of the software components
18 of 19
Regression testing
- Testing that software previously developed and tested still performs correctly after it was changed or interfaced with other software.
19 of 19
Other cards in this set
Card 2
Front
Performance testing
Back
- Determine how fast some aspect of a system performs under a certain workload - can demonstrate that the system meets performance criteria - compare two systems - can see what parts of the the system/workload caused issues
Comments
No comments have yet been made