NattyGraphicsTestPlan
Differences between revisions 38 and 43 (spanning 5 versions)
|
Size: 2881
Comment: page was renamed from QATeam/NattyProprietaryXDriversTestPlan
|
Size: 3928
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| == Purpose == The purpose of this document is to explain the different testing efforts for Unity in the Natty cycle. It is designed to prescribe the scope, approach, resources, and schedule for all testing activities during this cycle. |
|
| Line 9: | Line 7: |
| This document will be modified and enhanced as required throughout the verification testing engagement. The purpose of this document: * Defines the overall test approach. * Identifies software and system hardware to be tested. * Identifies hardware, software, and tools to be used to support the testing efforts. * Defines the types of tests to be performed. ''Note: Specific effort for regression testing ?'' |
== Objectives == The objective of this document is to define a test plan for ATI/NVidia proprietary driver testing and graphics and performance in Unity. |
| Line 19: | Line 11: |
The testing tasks for the components of Ubuntu includes: * Functional testing of the applications (automated and manual - Desktop Testing initiative) * Integration with the desktop environment * Unity * 2D Desktop (gnome fallback when 3D support is not available) * Server Testing * ISO Testing * Hardware Testing * Additional Testing: i18n, a11y, printing |
The testing tasks includes: * Testing of ATI and NVidia proprietary drivers * Test cases that are known for: * Crashes * Visual corruption * Performance impact |
| Line 31: | Line 19: |
| * Collect, provide and review Test Cases that uncover new bugs or cover existing known issues. | |
| Line 36: | Line 23: |
| Testing will be performed all along during the development cycle of Natty. The main milestones of the test plan are aligned on the [[https://wiki.ubuntu.com/NattyReleaseSchedule|Release Schedule]] and [[https://wiki.ubuntu.com/NattyReleaseInterlock|Natty Release Interlock]] Testing is a very dependant activity, As a result, test planning is a continuing activity performed throughout the system development life cycle. | == Deliverables == * This test plan * At the end of each testing milestone QA will provide a test report for that testing cycle. * All defects found will be reported in Launchpad. |
| Line 38: | Line 28: |
| ''Note: HW Testing -> Cert Team: to be included in this doc ?'' | = X Drivers Testing = |
| Line 40: | Line 30: |
| == Project Milestones / Schedule == | There are 11 test cases covering all aspects of the ATI and NVidia proprietary drivers, from installation, basic and standard functionalities (resolutions, rotation, monitor hot plugging,...) and removal of the drivers. |
| Line 42: | Line 32: |
| * [[https://wiki.ubuntu.com/NattyReleaseSchedule|Release Schedule]] * [[https://wiki.ubuntu.com/NattyReleaseInterlock|Natty Release Interlock]] |
They are available from [[http://testcases.qa.ubuntu.com/Hardware/X/ProprietaryDrivers|testcases.qa.ubuntu.com]] |
| Line 45: | Line 34: |
| = Test Items and Features = == New Features in Natty Narwhal (Ubuntu 11.04) == ''List the new features that need extensive testing'' |
= Unity Graphics Performance and reliability = |
| Line 49: | Line 36: |
| * GTK 3.0 with GObject Introspection is still a fairly young technology which is still in flux, so we need to regularly test our applications which got ported to it: * Apport: Try `ubuntu-bug audio` and select the "record" case, then follow the steps, and finally check if you get a reasonable output and behaviour of the details window (like unreasonable window size, or unreadable text). Please make sure to open the Details expander. |
== Running Autopilot == '''Case ID: ''' upr-001 1. Open a terminal 1. Run the command: * /usr/lib/unity/autopilot.py 1. Check that the result of the test is PASS == Compiz Scale == '''Case ID: ''' upr-002 1. Ubuntu Unity desktop, complete with decorations 1. Open up 2 instances of nautilus (both maximised) 1. Open up a gnome terninal window (unmaximised) - this is our visual test case 1. On Unity dock - Double click nautilus icon 1. Scale plugin activated 1. Focus back on terminal window, 1. Verify that the decorations are present = Target Hardware = == NVIDIA Cards == * GeForce 8m (8xxxM) * GeForce 9m (9xxxM) * GeForce 100M (1xxM) * GeForce 200M (2xxM) * GeForce 300M (3xxM) * GeForce 400M (4xxM) * GeForce 500M (5xxM) * + Mobile cards * And more generally all the graphics chips that are sold today by NVidia have the harware capabilities we need to run Unity. We can safely go as far as 5 years and the GPUs that were made by either of these companies will still offer the hardware features we need. == ATI Cards == * R6xx (HD 2xxx, HD 3xxx) * R7xx (HD 4xxx) * R8xx (HD 5xxx) "Evergreen" series * (HD 6xxx) "Northern Islands" series * + Mobile cards * And more generally all the graphics chips that are sold today by AMD have the harware capabilities we need to run Unity. We can safely go as far as 5 years and the GPUs that were made by either of these companies will still offer the hardware features we need. = Acceptance Criteria = == Alpha == The Phase 1 Alpha deliverable will be considered met when all the basic functionality of the software and hardware is complete. The client will have the ability to test the deliverable software and hardware functionality. There may be defects in this milestone that will be addressed in the next Phase. Performance and reliability requirements are out of scope for the Alpha release. The image may have Critical, High and Medium bugs. == Acceptance Criteria: Phase 2 - Beta == The Phase 2 Beta release will be considered feature complete based on the Statement of Work. This image will also include bug fixes. The image may have a limited number of Critical bugs. Performance and reliability requirements are acceptable for the Beta release. == Acceptance Criteria: Phase 3 – Final Release == This image will be the Final release. All features will be complete. There are no Critical bugs. A minimum of High level bugs may be present. |
Introduction
Objectives
The objective of this document is to define a test plan for ATI/NVidia proprietary driver testing and graphics and performance in Unity.
Scope
The testing tasks includes:
- Testing of ATI and NVidia proprietary drivers
- Test cases that are known for:
- Crashes
- Visual corruption
- Performance impact
For each testing task we will also:
- Collect test data and review testing results.
- Reporting of all test results.
- Risk analysis and communication of the blocking issues.
Deliverables
- This test plan
- At the end of each testing milestone QA will provide a test report for that testing cycle.
- All defects found will be reported in Launchpad.
X Drivers Testing
There are 11 test cases covering all aspects of the ATI and NVidia proprietary drivers, from installation, basic and standard functionalities (resolutions, rotation, monitor hot plugging,...) and removal of the drivers.
They are available from testcases.qa.ubuntu.com
Unity Graphics Performance and reliability
Running Autopilot
Case ID: upr-001
- Open a terminal
- Run the command:
- /usr/lib/unity/autopilot.py
- Check that the result of the test is PASS
Compiz Scale
Case ID: upr-002
- Ubuntu Unity desktop, complete with decorations
- Open up 2 instances of nautilus (both maximised)
- Open up a gnome terninal window (unmaximised) - this is our visual test case
- On Unity dock - Double click nautilus icon
- Scale plugin activated
- Focus back on terminal window,
- Verify that the decorations are present
Target Hardware
NVIDIA Cards
GeForce 8m (8xxxM)
GeForce 9m (9xxxM)
GeForce 100M (1xxM)
GeForce 200M (2xxM)
GeForce 300M (3xxM)
GeForce 400M (4xxM)
GeForce 500M (5xxM)
- + Mobile cards
- And more generally all the graphics chips that are sold today by NVidia have the harware capabilities we need to run Unity. We can safely go as far as 5 years and the GPUs that were made by either of these companies will still offer the hardware features we need.
ATI Cards
- R6xx (HD 2xxx, HD 3xxx)
- R7xx (HD 4xxx)
- R8xx (HD 5xxx) "Evergreen" series
- (HD 6xxx) "Northern Islands" series
- + Mobile cards
- And more generally all the graphics chips that are sold today by AMD have the harware capabilities we need to run Unity. We can safely go as far as 5 years and the GPUs that were made by either of these companies will still offer the hardware features we need.
Acceptance Criteria
Alpha
The Phase 1 Alpha deliverable will be considered met when all the basic functionality of the software and hardware is complete. The client will have the ability to test the deliverable software and hardware functionality. There may be defects in this milestone that will be addressed in the next Phase. Performance and reliability requirements are out of scope for the Alpha release.
The image may have Critical, High and Medium bugs.
Acceptance Criteria: Phase 2 - Beta
The Phase 2 Beta release will be considered feature complete based on the Statement of Work. This image will also include bug fixes. The image may have a limited number of Critical bugs. Performance and reliability requirements are acceptable for the Beta release.
Acceptance Criteria: Phase 3 – Final Release
This image will be the Final release.
All features will be complete. There are no Critical bugs. A minimum of High level bugs may be present.
QATeam/NattyGraphicsTestPlan (last edited 2011-03-17 17:01:13 by ACaen-151-1-93-135)