Risk | Test measure (section number/s) |
Response times result in problems: – Too high – Increase too much at expected peaks – Increase too much at unexpected peaks |
5.2 |
Processing capacity (throughput) is insufficient. | 5.2.1 |
Upload/download speed (bandwidth) is insufficient: – On supplier side – On customer side |
5.1.3, 5.2.1 5.2 |
Other customers affect performance. | 5.1.3, 5.2.1, 5.2.4 |
Performance is insufficient due to overbooking at supplier side. | 5.2.1, 5.9.2 |
Performance is not sufficient on all types of devices. | 5.2, 5.9.2 |
Customer experiences performance is insufficient. | 5.1.3, 5.2.1 |
Scaling does not suffice: – Scaling up manually does not work. – Scaling down manually does not work. – Manual scaling causes disruptions. – Scaling up automatically does not work. – Scaling down automatically does not work. – Automatic scaling causes disruptions. – Insufficient growth potential. |
5.1.3, 5.2.4 |
Performance varies due to Internet connection. | 5.2, 5.9.1, 5.9.2 |
Performance decreases due to changes by supplier. | 5.2, 5.9.1, 5.9.2 |
Performance deteriorates over time. | 5.2.3, 5.9.1, 5.9.2 |
User demands change over time. | 5.9.3 |
Pay per use not accurate enough: – Paid too much – Too little transparency |
5.2.4, 5.9.2, 5.1.3 |
Latency (delay) is too high: – Insufficient performance – Technical issues in the service – Technical issues in the interfaces – Technical issues in interfacing systems |
5.2, 5.9.2 |
Performance is not sufficient throughout the world. | 5.2.7 |
User experiences quality of video or audio as low. | 5.2 |
User requirements for performance are not clear. | 5.1.2, 5.2.5 |
Executing performance tests is not possible. | 5.1.3, 5.4.4 |
Performance tests are not representative. | 5.2.11, 5.4.4 |
Terug naar Testing cloud services | Terug naar From risk to test