QA Procedures: Difference between revisions
From Xen
Jump to navigationJump to search
Lars.kurth (talk | contribs) (Migrated) |
m (avilable -> available) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 16: | Line 16: | ||
There is already some work being done in these areas, but it's not centrally coordinated - as to my knowledge, some businesses run their internal testing farms and regularly tests some areas of the Xen code. All these efforst could be coordinated or at least documented centrally at this page. |
There is already some work being done in these areas, but it's not centrally coordinated - as to my knowledge, some businesses run their internal testing farms and regularly tests some areas of the Xen code. All these efforst could be coordinated or at least documented centrally at this page. |
||
= Coordination = |
= Coordination and other resources = |
||
As of yet, the following pages are |
As of yet, the following pages are available: |
||
* [[XenTest]] - Testing Xen regularly and automatically |
* [[XenTest]] - Testing Xen regularly and automatically |
||
* [[BugManagement]] - tracking and handling bugs and information about them efficiently |
* [[BugManagement]] - tracking and handling bugs and information about them efficiently |
||
* [[ReportingBugs]] - how to report bugs |
|||
[[Category:Xen]] |
[[Category:Xen]] |
||
Latest revision as of 23:45, 29 November 2011
Introduction
This page provides information about QA procedures of the GPL releases of Xen.
One of the first and currently most important tasks not handled as of yet for this team is taking care of Xen's Bug database, the tasks for this are described on the page BugManagement. Apart from that, if we have more time to invest, there could be many more tasks done (some describedhere), like:
- Adding missing unit tests for the python tools (and checking the code coverage state of the current code)
- Setting up automated test systems for as much functions as possible, and as much different combinations of hardware and software configurations
- ...
There is already some work being done in these areas, but it's not centrally coordinated - as to my knowledge, some businesses run their internal testing farms and regularly tests some areas of the Xen code. All these efforst could be coordinated or at least documented centrally at this page.
Coordination and other resources
As of yet, the following pages are available:
- XenTest - Testing Xen regularly and automatically
- BugManagement - tracking and handling bugs and information about them efficiently
- ReportingBugs - how to report bugs
