From Fedora Project Wiki
(New page: = Quality Assurance = == Summary == Bringing current QA project to [ http://en.wikipedia.org/wiki/Software_Quality_Assurance SQA ] == Owner == * Name: [[User:Johannbg| Jóhann Benedi...)
 
No edit summary
Line 23: Line 23:


'''SQC'''
'''SQC'''
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... 


* Improving documentation on the wiki
* Improving documentation on the wiki
( How to etc )
* Create a calender on the wiki which project assign them self to a certain time slots and what to test
* Create a calender on the wiki which project assign them self to a certain time slots and what to test  
( Takes test days to next level ). 
* Build an automated test system.
* Build an automated test system.
* Increase communication with testers.
* Build a better/more active test community.
( Meetings agenda for example etc. )
* Get developers to redirect test traffic from the devel-list to the test-list
* 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 debugin testing etc see
[[Anaconda|Anaconda]] for example. VERY VITAL THAT THIS IS ACHIEVED.




== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
*Improved Documentation
*Proper QA process
*Better bug reports
*Better testing.
 


== Scope ==
== Scope ==
Line 55: Line 64:


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
The project itself will get a more professional QA.
Developers will get better bug reports.
Tester will learn more.


== Dependencies ==
== Dependencies ==

Revision as of 17:39, 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 a summary of what I had written...

  • 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 debugin 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=57954"