NattyGraphicsTestPlan
Differences between revisions 1 and 39 (spanning 38 versions)
|
Size: 3154
Comment: Added Draft for Natty TestPlan
|
Size: 1587
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| /!\ '''DRAFT''' == Summary == |
## page was renamed from QATeam/NattyProprietaryXDriversTestPlan ## page was copied from QATeam/NattyTestPlan ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 4: | Line 5: |
| The purpose of this document is to explain the different testing efforts for Unity in the Natty cycle. | = Introduction = |
| Line 6: | Line 7: |
| == Automated 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 8: | Line 10: |
| === Unity itself === | == 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 10: | Line 15: |
| Although the DX team is the main responsible of testing the Unity interface itself, we need to collaborate with them so our tests work better. | == Scope == |
| Line 12: | Line 17: |
| Unity itself is not accessible, so the Unity interface cannot be accessed directly with the tools we have right now. Luckily, [[http://mago.ubuntu.com|Mago]] is tool agnostic and, although is mostly based on [[http://ldtp.freedesktop.org/|LDTP]], we can add other tools to help us testing the interface itself. | The testing tasks includes: * Testing of ATI and NVidia proprietary drivers * Test cases that are known for: * Crashes * Visual corruption * Performance impact |
| Line 14: | Line 24: |
| The Unity team will provide with a dbus interface that will allow us knowing the state of the interface at any given time. That will help us checking if the icons are showing correctly. | 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. |
| Line 16: | Line 29: |
| [[https://wiki.ubuntu.com/Xpresser|Xpresser]], which is based in image comparison, is not suitable to check the state of Unity after running a test, as the design will change a lot during the Natty cycle. | = Test Items and Features = == New Features in Natty Narwhal (Ubuntu 11.04) == ''List the new features that need extensive testing'' |
| Line 18: | Line 33: |
| === Applications on Unity === The applications on Unity can be tested using the same a11y tools that we already use for the 2D experience. One of the main caveats is that Unity does not run under Xvfb and, therefore, we cannot run it on a server without having a full desktop up and running. * Research on how to run the tests using Hudson (or something else) in an automated fashion * Run the mago tests on Unity twice per week in a machine with Unity running as mean time solution * The tests results will be publicly available Xpresser, although based in image comparison, can be good to launch applications from the launcher, as it is not accessible yet, and the icons don't tend to change that much. We need to be careful, though, as Xpresser is not being actively maintained and there could be some bugs. === 2D Experience === The 2D experience needs to be tested as well and, actually, as the 2D experience runs well in a Xvfb, it will be easier to run using Hudson, without ==== ACTIONS ==== * Run a Hudson server on the datacenter * Run a cronjob to update the system on a daily basis * Run the mago tests on a daily basis in an automated fashion == Manual Testing == === ISO Testing === As part as our per milestone testing, we need to be testing Unity on desktops and the 2D experience fallback. Many of us use VMs to test the images and we need to find a VM technology capable of running Unity. Also, we need to modify the testcases (or add new ones) to match the new possibilities. ==== ACTIONS ==== * Communication with the installer and design teams to modify the testcases * Include the new testcases into the ISO tracker === Desktop Testing Program === The Desktop Testing Program started last cycle and it provided a good way for the community to test the desktop applications every milestone. As part of the modifications for this program in the Natty cycle, we will be including Unity as part of the program. For each of the applications, we will be duplicating the testcases, to be run in Unity and also the 2D experience. |
* 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. |
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)