NattyGraphicsTestPlan
Differences between revisions 38 and 39
|
Size: 2881
Comment: page was renamed from QATeam/NattyProprietaryXDriversTestPlan
|
Size: 1587
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: | == 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 11: | Line 10: |
| * 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 ?'' |
== 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 20: | Line 17: |
| 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 25: |
| * Collect, provide and review Test Cases that uncover new bugs or cover existing known issues. | |
| Line 35: | Line 28: |
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. ''Note: HW Testing -> Cert Team: to be included in this doc ?'' == Project Milestones / Schedule == * [[https://wiki.ubuntu.com/NattyReleaseSchedule|Release Schedule]] * [[https://wiki.ubuntu.com/NattyReleaseInterlock|Natty Release Interlock]] |
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.
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.
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.
Test Items and Features
New Features in Natty Narwhal (Ubuntu 11.04)
List the new features that need extensive testing
- 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.
QATeam/NattyGraphicsTestPlan (last edited 2011-03-17 17:01:13 by ACaen-151-1-93-135)