Difference between revisions of "QA"
(Added existed useful articles) |
(Removed underscores in links) |
||
| Line 23: | Line 23: | ||
* [[Reporting_OpenVZ_problem|Reporting bugs]] | * [[Reporting_OpenVZ_problem|Reporting bugs]] | ||
| − | * [[Known_problems| | + | * [[Known_problems|Known problems]] |
| − | * [[Kernel_debug_options| | + | * [[Kernel_debug_options|Kernel debug options]] |
| − | * [[When_you_have_an_oops| | + | * [[When_you_have_an_oops|When you have an oops]] |
| − | * [[Kernel_versioning| | + | * [[Kernel_versioning|Kernel versioning]] |
Revision as of 17:41, 9 March 2015
Each more or less complex project requires testing. OpenVZ is not an exception here.
This is a homepage of OpenVZ QA Team. The OpenVZ Quality Assurance team is focused on developing and maintaining different kinds of tests for ensuring OpenVZ's quality as well as providing general advice, oversight, and leadership of QA community and its activities within the OpenVZ project.
Getting Involved
You can get involved with the OpenVZ Quality team in several ways. To help you get started, we have split the tasks in several roles: Tester and TestWriter.
Useful articles
Resources:
- Automatic testing of Parallels Cloud Server - PCS is a commercial version of OpenVZ. It may be interesting how commercial version tested by Parallels QA Team.
- r/fosstesting - stories about testing in another opensource projects.
- Small description of in-house testing written by Kir
