|
|
| Line 1: |
Line 1: |
| {{admon/caution|This is a draft|This is a draft of a document that may or may not be migrated into a more sane namespace.}} | | {{header|qa}} |
|
| |
|
| = Introduction =
| |
|
| |
|
| This document describes the test process by which Fedora 10 will be verified for operation consistent to that of other common laptop hardware.
| | = Fedora Quality Assurance = |
|
| |
|
| The goals of this plan are to:
| | Fedora is a rapidly progressing distribution and collection of free software. We have detailed quality assurance procedures to help maintain a cutting edge, innovating and a robust platform which consist of people like you and me from around the world. |
|
| |
|
| * Organize a community test effort
| | == Teams == |
| * Communicate the strategy, scope and priorities of the planned tests to all relevant stake-holders for their input and approval
| |
| * Serve as a base for the test planning for future Fedora releases
| |
|
| |
|
| {{admon/important|FIXME - Outline exit criteria|What bugs should be prioritized by development? How do we know if something should be fixed or not?}}
| | What we do can be broken down to several categories, including: |
|
| |
|
| = Strategy =
| | * [[QA/BugHunters|Bug Hunters]] - tasked to find bugs |
| | * [[BugZappers|Bug Zappers]] - tasked with helping bugs navigate through |
|
| |
|
| In an effort to focus testing on specific XO hardware, the test strategy will be to:
| | == Communicate == |
| # Define a set of high-level test areas that group similar functional components together
| |
| # Organize volunteers into teams, each team focused on a specific test area
| |
| # Teams will develop a rough test plan for their test area. Each team can dictate the required level of testing (both in terms of depth and breadth)
| |
|
| |
|
| As no centralized automation is available, test teams are encouraged to leverage [http://en.wikipedia.org/wiki/Exploratory_testing exploratory testing] and built-in unit-tests where possible.
| | * [[QA/Meetings|Attend a QA Team meeting]] |
| | * [mailto:fedora-test-list@redhat.com Send mail to fedora-test-list@redhat.com] |
| | * [irc://irc.freenode.net/fedora-qa Talk directly with other testers in #fedora-qa] on [[Communicate/IRC|IRC]] |
|
| |
|
| Use existing tools to facilitate writing new test builds to the XO's SD card (see ''livecd-iso-to-disk.sh'').
| | == Get Involved == |
|
| |
|
| = Schedule =
| | * Join a QA team (see above) |
| | | * [http://join.fedoraproject.org Not interested in QA, take a look at other Fedora projects] |
| An up-to-date schedule for Fedora 10 is available at [[Releases/10/Schedule]]. A summary of Fedora XO related test milestones is noted below.
| |
| | |
| {|
| |
| ! Date !! Milestone
| |
| |-
| |
| | Tue 2008-09-30 || Public beta
| |
| |-
| |
| | Fri 2008-10-10 || Snapshot#1
| |
| |-
| |
| | Fri 2008-10-17 || Snapshot#2
| |
| |-
| |
| | Fri 2008-10-24 || Snapshot#3
| |
| |-
| |
| | Tue 2008-11-04 || Preview release
| |
| |-
| |
| | Tue 2008-11-25 || General Availability
| |
| |-
| |
| |}
| |
| | |
| = Scope =
| |
| | |
| The scope of all testing should be representative of the XO hardware under test. No need to test Gigabit ethernet if the XO doesn't provide such an adapter. See the test area break down for more details.
| |
| | |
| Items '''not''' tested:
| |
| * Installation of Fedora on an XO - only live image booting from the SD is planned for Fedora 10 | |
| | |
| {{admon/important|FIXME|Do we need to test persistent storage on the live image?}}
| |
| | |
| = Test Areas =
| |
| | |
| == [[QA/TestPlans/Camera | Built-in Camera]] ==
| |
| | |
| * What applications can be used to verify the camera?
| |
| * Laptop microphone/camera in-use indicators behave as expected
| |
| | |
| == [[QA/TestPlans/Power Management | Power Management]] ==
| |
| | |
| * Suspend/resume
| |
| * Hibernate
| |
| ** close lid
| |
| ** low battery
| |
| * Use and report findings from ''powertop''
| |
| ** Measure battery usage?
| |
| * Display brightness configuration (dim when idle)
| |
| * Remove/add power adapter while running
| |
| * Laptop Power/battery indicators behave as expected
| |
| | |
| == [[QA/TestPlans/Networking | Networking]] ==
| |
| | |
| * Wireless networking
| |
| ** laptop wifi status indicator behaves as expected
| |
| ** firmware loaded by NM
| |
| ** can connect using various methods (None/WEP/WPA)
| |
| ** VPN?
| |
| ** Sharing an ad-hoc network w/ another XO
| |
| | |
| == [[QA/TestPlans/Display | Display]] ==
| |
| | |
| * xrandr rotation?
| |
| * Using expected driver and resolution settings
| |
| * Changing vt's back and forth
| |
| * Coming out of suspend?
| |
| * touchpad interface?
| |
| * gamepad interface?
| |
| * Brightness up/down accelerator key?
| |
| * plymouth graphical boot enabled+working by default?
| |
| | |
| == [[QA/TestPlans/Audio | Audio]] ==
| |
| | |
| * pulse audio default settings (not muted)
| |
| * various mixer settings visible/editable (ala ''gnome-volume-control'')
| |
| * gnome system sounds enabled
| |
| * Recording (ala ''gnome-sound-recorder'')
| |
| * headphone jack / internal speaker
| |
| * Volume up/down accelerator key?
| |
| | |
| == Miscellaneous ==
| |
| | |
| * test USB port
| |
| * Anything specific to boot processing (plymouth noted above)
| |
| * Default configured services?
| |
| | |
| = Responsibilities =
| |
| | |
| This section outlines the test teams and various community points of contact.
| |
| | |
| * [[User:gdk]] | |
| * [[User:katzj]]
| |
| * [[User:jlaska]]
| |
| | |
| Each test area is being split up for a different team of experts to deep dive into. The table below will be used to outline the teams and their focus areas.
| |
| | |
| {|
| |
| ! Test Area !! Team Name !! Team Members
| |
| |-
| |
| | Example: Orbital Laser
| |
| | Team Dunder Mifflin
| |
| | Jim, Pam, Stanley
| |
| |-
| |
| | Built-in Camera
| |
| |
| |
| |
| |
| |-
| |
| | Power Management
| |
| |
| |
| |
| |
| |-
| |
| | Networking
| |
| |
| |
| |
| |
| |-
| |
| | Display
| |
| |
| |
| |
| |
| |-
| |
| | Audio
| |
| |
| |
| |
| |
| |-
| |
| |}
| |
| | |
| = HOWTO's =
| |
| | |
| The following sections are intended to provide high-level instructions for common tasks encountered by a Fedora XO tester.
| |
| | |
| == File Fedora XO bugs ==
| |
| | |
| All bugs will be tracked in [[Bugzilla]].
| |
| | |
| Please file all bugs found while testing Fedora on the XO with the following parameters:
| |
| * ''product'' = '''Fedora'''
| |
| * ''version'' = '''rawhide'''
| |
| * ''blocks'' = '''[[rhbug:461806|FedoraOnXO]]'''
| |
| | |
| For convenience, you can file an new Fedora XO bug by [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&blocked=FedoraOnXO clicking here].
| |
| | |
| == Triage NEW Fedora XO Bugs ==
| |
| | |
| To help with triaging ...
| |
| | |
| # Start with the list of '''NEW''' Fedora XO bugs at http://tinyurl.com/52wclh
| |
| | |
| For each bug, ask yourself the following questions:
| |
| | |
| # Is the bug specific to the XO hardware or environment?
| |
| # Was the following information provided?
| |
| #* Build tested (rawhide-YYYYMMDD or package versions)
| |
| #* Clear steps to reproduce the problem
| |
| | |
| If the above requirements have been met, please:
| |
| # Mark the bug as blocking [[rhbug:FedoraOnXO|461806 (FedoraOnXO)]]
| |
| # Change to bug state to '''ASSIGNED'''
| |
| | |
| For further reading, the bug triage process is described in more detail at [[BugZappers]].
| |
| | |
| ==Test a MODIFIED Fedora XO Bug ==
| |
| | |
| FIXME - provide tinyurl link to MODIFIED Fedora XO Bugs
| |
| | |
| Ask the following questions:
| |
| | |
| # Are you able to confirm that the steps to reproduce no longer trigger the failure?
| |
| # Have any new bugs been introduced as a result of the fix?
| |
| # Are any release notes required?
| |
| | |
| When comfortable with the fix:
| |
| | |
| # Add a comment indicating which build or software packages were tested
| |
| # Change the bug state to '''CLOSED''' with a resolution of '''RAWHIDE'''
| |
| | |
| If the reported issue has not been addressed:
| |
| | |
| # Add a comment indicating which build or software packages were tested that still exhibit the failure
| |
| # Change the state to '''ASSIGNED'''
| |
| | |
| = Documentation =
| |
| | |
| == Getting Started ==
| |
| | |
| {{admon/important|FIXME|need more docs!}}
| |
| | |
| * What are we trying to accomplish?
| |
| ** Overview posted at [[OLPC/Fedora_on_XO]]
| |
| | |
| * What are the requirements for testing?
| |
| ** List matching hardware
| |
| ** Known issues on older XO's?
| |
| | |
| * How to sign-up for a team?
| |
| * How to communicate issues?
| |
| | |
| * Where to go for help?
| |
| ** fedora-test-list
| |
| ** #fedora-qa
| |
| | |
| * Where are test images posted?
| |
| | |
| == Installing your SD card ==
| |
| | |
| Requirements:
| |
| * Another computer to flash the SD card
| |
| * SD reader
| |
| * SD card - specifically a Sandisk Extreme III SD card (either [http://www.sandisk.com/Products/Item(1973)-SDSDX3-2048-SanDisk_Extreme_III_SD_2GB.aspx 2 Gig] or [http://www.sandisk.com/Products/ProductInfo.aspx?ID=2348 4 Gig] capacity).
| |
| * An internet connection
| |
| | |
| To install a live image to your SD card:
| |
| # Download the installation script: <pre># wget http://katzj.fedorapeople.org/olpc/livecd-iso-to-disk.sh</pre>
| |
| # Download an OLPC Fedora Live image from: <pre># wget http://katzj.fedorapeople.org/olpc/olpc-gnome.iso</pre>
| |
| # Write the live image to your SD card: <pre># bash livecd-iso-to-disk.sh --extra-kernel-args 3 --xo-sd olpc-gnome.iso /path/to/sd/device</pre>
| |
| | |
| == Getting a Developer Key ==
| |
| | |
| {{admon/important|FIXME|need more details on the background and process from edmcnierney.}}
| |
