(→Strategy and Approach) |
(→Strategy and Approach) |
||
| Line 11: | Line 11: | ||
=== Strategy and Approach === | === Strategy and Approach === | ||
| + | Non-functional testing can be divided in higher level to two different areas: performance and reliability testing. MeeGo release will be tested in different NFT test sets both from performance and reliability perspective. Test areas that will be used: | ||
* Performance testing | * Performance testing | ||
| Line 22: | Line 23: | ||
*** Amount of (RAM) memory used during a use case or over a period of time | *** Amount of (RAM) memory used during a use case or over a period of time | ||
** Performance Snapshot | ** Performance Snapshot | ||
| - | *** Test set consisting of couple test cases from all performance areas defined above | + | *** The purpose of Non-Functional performance snapshot is to give a clear and immediate overview of the software being tested in terms of non-functional errors and efficiency from end user perspective. Test set is consisting of couple test cases from all performance areas defined above |
* Reliability testing | * Reliability testing | ||
** Aging | ** Aging | ||
Contents |
Non-functional testing can be divided in higher level to two different areas: performance and reliability testing. MeeGo release will be tested in different NFT test sets both from performance and reliability perspective. Test areas that will be used: