From Fedora Project Wiki
No edit summary
No edit summary
Line 24: Line 24:
'''SQC'''
'''SQC'''


Oh great time out in the wiki on what I had written teaches me to save more often
Oh great time out in the wiki on what I had written teaches me to save more often.
Here a summary of what I had written...   
 
Here's sum of what I had written hit me with questions and I will answer...   


* Improving documentation on the wiki
* Improving documentation on the wiki
Line 34: Line 35:
* Get Gnome/KDE/XFCE etc to have something like properties item which would show what's being executed and perhaps  
* Get Gnome/KDE/XFCE etc to have something like properties item which would show what's being executed and perhaps  
to which package it belongs to get correcter bug reports.
to which package it belongs to get correcter bug reports.
* Create each listen "component" in bugzilla to have it's own wiki page with relevant info on debugin testing etc see  
* Create each listen "component" in bugzilla to have it's own wiki page with relevant info on debuging testing etc see  
[[Anaconda|Anaconda]] for example. VERY VITAL THAT THIS IS ACHIEVED.
[[Anaconda|Anaconda]] for example. VERY VITAL THAT THIS IS ACHIEVED.


Line 47: Line 48:


== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 


== Test Plan ==
== Test Plan ==
Line 70: Line 71:


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
 


== Contingency Plan ==
== Contingency Plan ==

Revision as of 17:46, 4 November 2008

Quality Assurance

Summary

Bringing current QA project to [ http://en.wikipedia.org/wiki/Software_Quality_Assurance SQA ]

Owner

Current status

  • Targeted release: Fedora 11
  • Last updated: 2008-11-04
  • Percentage of completion: 01%

Detailed Description

QA

  • Creation of QA board which would be elected or otherwise selected individuals from each "sub project"
  • Fesco could be that board.

SQC

Oh great time out in the wiki on what I had written teaches me to save more often.

Here's sum of what I had written hit me with questions and I will answer...

  • Improving documentation on the wiki
  • Create a calender on the wiki which project assign them self to a certain time slots and what to test
  • Build an automated test system.
  • Build a better/more active test community.
  • Get developers to redirect test traffic from the devel-list to the test-list
  • Get Gnome/KDE/XFCE etc to have something like properties item which would show what's being executed and perhaps

to which package it belongs to get correcter bug reports.

  • Create each listen "component" in bugzilla to have it's own wiki page with relevant info on debuging testing etc see

Anaconda for example. VERY VITAL THAT THIS IS ACHIEVED.


Benefit to Fedora

  • Improved Documentation
  • Proper QA process
  • Better bug reports
  • Better testing.


Scope

Test Plan

User Experience

The project itself will get a more professional QA. Developers will get better bug reports. Tester will learn more.

Dependencies

Contingency Plan

Keep the process as is...

Documentation

QA Will hold the new QA wikipage along with it sub pages.. Hack at will...


Release Notes

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/QA&oldid=57959"