From Fedora Project Wiki

m (1 revision(s))
m (Fixed template and links)
Line 1: Line 1:
= Fedora Testing =
= Fedora Testing =


{| border="1"
{{Old | This page is somewhat out of date - see [[QA]] for better info!}}
|-
| {{Template:Warning}} This page is somewhat out of date - see ["QA"] for better info!
|}
 
 


== Our Mission ==
== Our Mission ==
Line 16: Line 11:
* Fearless Leader: WillWoods
* Fearless Leader: WillWoods
* Official business conducted on fedora-test-list (see http://www.redhat.com/mailman/listinfo/fedora-test-list)
* Official business conducted on fedora-test-list (see http://www.redhat.com/mailman/listinfo/fedora-test-list)
* General project discussion goes on in #fedora-qa (see ["Communicate/IRCHowTo"] )
* General project discussion goes on in #fedora-qa (see [[Communicate/IRCHowTo]] )
* Sub-projects may have their own leaders, who should regularly report on the status of their project.
* Sub-projects may have their own leaders, who should regularly report on the status of their project.
* Subproject suggestions are cheerfully accepted!
* Subproject suggestions are cheerfully accepted!


== Meetings ==
== Meetings ==


* http://fedoraproject.org/wiki/QA/Meetings
* [[QA/Meetings]]




Line 29: Line 23:


1. Test Plans for Fedora components
1. Test Plans for Fedora components
* ["QA/ReleaseCriteria"]  is used as a base for creating release test plans.
* [[QA/ReleaseCriteria]]  is used as a base for creating release test plans.
* ["QA/FC6TreeTesting"]  is the most recently-used release test plan.
* [[QA/FC6TreeTesting]]  is the most recently-used release test plan.
* [http://fedoraunity.org/ Fedora Unity]  has a [http://torrent.fedoraunity.org/unity/fedora-core-5-unity-respin-20060621 test plan for their respin release]  
* [http://fedoraunity.org/ Fedora Unity]  has a [http://torrent.fedoraunity.org/unity/fedora-core-5-unity-respin-20060621 test plan for their respin release]  
* ["QA/HowToTestTemplate"]  is a test plan template for an individual package.
* [[QA/HowToTestTemplate]]  is a test plan template for an individual package.
* Write a Xen test plan
* Write a Xen test plan
* Identify "tiers" of functionality - Tier1 = most important (system boots, etc.)
* Identify "tiers" of functionality - Tier1 = most important (system boots, etc.)
Line 38: Line 32:
* Include documentation on how to test, like AnacondaHowToTest
* Include documentation on how to test, like AnacondaHowToTest
* Put together a central tracker for test plans and testing progress
* Put together a central tracker for test plans and testing progress
1. Executing test plans
*# Executing test plans
* Volunteers! We'll need volunteers!
* Volunteers! We'll need volunteers!
* We may run Bug Days where everyone takes a test plan and runs with it.
* We may run Bug Days where everyone takes a test plan and runs with it.
1. BugZappers
*# BugZappers
* Revive Bug Days!
* Revive Bug Days!
* Make Bugzilla send out weekly reports of new bugs, bugs closed, etc. to fedora-triage-list
* Make Bugzilla send out weekly reports of new bugs, bugs closed, etc. to fedora-triage-list
* BugZappers leaders can split up the weekly list, or choose a category of bugs to focus on
* BugZappers leaders can split up the weekly list, or choose a category of bugs to focus on
1. Bug Hunts
*# Bug Hunts
* Like ["QA/FixBuildRequires"]  - an ongoing project with a single focus.
* Like [[QA/FixBuildRequires]]  - an ongoing project with a single focus.
* Karma system - submitting or fixing a bug gets you karma points, which gets you Cool Stuff.
* Karma system - submitting or fixing a bug gets you karma points, which gets you Cool Stuff.
1. "Hot Issues" page - see ["Bugs/FC6Common"]  
*# "Hot Issues" page - see [[Bugs/FC6Common]]
* A listing of current Fedora issues with workarounds and ETA on fixes.
* A listing of current Fedora issues with workarounds and ETA on fixes.
* Linked to from the builtin FAQ page?
* Linked to from the builtin FAQ page?
1. Bugzilla RPG!
*# Bugzilla RPG!


== Possible Future Projects ==
== Possible Future Projects ==


1. Beaker, an automated test system
# Beaker, an automated test system
* see ["QA/Beaker"]  
#* see [[QA/Beaker]]
1. Extending automated testing
# Extending automated testing
* Try to automate test plans that we write, to reduce load on testers.
#* Try to automate test plans that we write, to reduce load on testers.
1. A bug-submittal app
# A bug-submittal app
* Provides a nice, easy interface to Bugzilla
#* Provides a nice, easy interface to Bugzilla
* Finds common issues (like from HotIssues above) and shows them to the user, to reduce dupes
#* Finds common issues (like from HotIssues above) and shows them to the user, to reduce dupes
* Use for crash reporting - automatically fills in component
#* Use for crash reporting - automatically fills in component
1. Performance testing
# Performance testing
* Run benchmarks
#* Run benchmarks
* Gather profiling data
#* Gather profiling data
* Gather information about how people typically use the software
#* Gather information about how people typically use the software
* Report findings to developers
#* Report findings to developers


== Other Stuff We Need (Join the Project) ==
== Other Stuff We Need (Join the Project) ==

Revision as of 23:04, 2 June 2008

Fedora Testing

Important.png
Old page
This page has been marked as "old", and likely contains content that is irrelevant or incorrect. If you can, please update this page. This page will be deleted if action is not taken.

Our Mission

To use and make free and open source software tests, testing tools, and test processes in order to make Fedora (and, by extension, all free and open source software) more awesome.

About the Project

Meetings


Current Subprojects

1. Test Plans for Fedora components

  • QA/ReleaseCriteria is used as a base for creating release test plans.
  • QA/FC6TreeTesting is the most recently-used release test plan.
  • Fedora Unity has a test plan for their respin release
  • QA/HowToTestTemplate is a test plan template for an individual package.
  • Write a Xen test plan
  • Identify "tiers" of functionality - Tier1 = most important (system boots, etc.)
  • Write more detailed test plans for important apps (Firefox, Evolution, etc.)
  • Include documentation on how to test, like AnacondaHowToTest
  • Put together a central tracker for test plans and testing progress
    1. Executing test plans
  • Volunteers! We'll need volunteers!
  • We may run Bug Days where everyone takes a test plan and runs with it.
    1. BugZappers
  • Revive Bug Days!
  • Make Bugzilla send out weekly reports of new bugs, bugs closed, etc. to fedora-triage-list
  • BugZappers leaders can split up the weekly list, or choose a category of bugs to focus on
    1. Bug Hunts
  • Like QA/FixBuildRequires - an ongoing project with a single focus.
  • Karma system - submitting or fixing a bug gets you karma points, which gets you Cool Stuff.
    1. "Hot Issues" page - see Bugs/FC6Common
  • A listing of current Fedora issues with workarounds and ETA on fixes.
  • Linked to from the builtin FAQ page?
    1. Bugzilla RPG!

Possible Future Projects

  1. Beaker, an automated test system
  2. Extending automated testing
    • Try to automate test plans that we write, to reduce load on testers.
  3. A bug-submittal app
    • Provides a nice, easy interface to Bugzilla
    • Finds common issues (like from HotIssues above) and shows them to the user, to reduce dupes
    • Use for crash reporting - automatically fills in component
  4. Performance testing
    • Run benchmarks
    • Gather profiling data
    • Gather information about how people typically use the software
    • Report findings to developers

Other Stuff We Need (Join the Project)

  • Testing volunteers
  • Further ideas for testing/QA projects
  • Volunteers to run subprojects
  • Roadmaps for other subprojects
  • More volunteers!

Please email WillWoods (or find him on IRC) if you are interested in making Fedora a better place!

Retrieved from "https://fedoraproject.org/w/index.php?title=FedoraTesting&oldid=30975"