MeeGo 1.2 HandSet UX Test Plan for System Non-Functional Test Plan
Component Summary
Features To Be Tested
Currently we are missing specific Non-Functional Requirements (NFR). These consists of target values for response times, frame rates, memory and power consumption, data throughput, etc.
NFRs are currently under planning and when defined they will be added here.
Features Not To Be Tested
Strategy and Approach
Non-functional testing (NFT) 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
- Power Management
- Measuring (average) current consumption of the device during a use case / over a period of time
- Data Throughput
- The (average) rate of successful message delivery over a communication channel in a given period of time
- Response Time
- Response time testing measures the time a system takes to react to given input by end-user; the total time it takes from a user request until response is received
- Memory Consumption
- Amount of (RAM) memory used during a use case or over a period of time
- Performance Snapshot
- 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
- Aging
- Measures the effect of long term usage for SW reliability and performance
- Iterative
- Performing multiple iterations of the same test case in order to expose possible problems in sequential runs
Hardware Platforms
QA Contact