Difference between revisions of "QA"
(Removed underscores) |
(Add hardware testing to useful articles) |
||
| Line 35: | Line 35: | ||
* [[Processes in D state]] | * [[Processes in D state]] | ||
* [[Remote console setup]] | * [[Remote console setup]] | ||
| + | * [[Hardware testing]] | ||
== External links == | == External links == | ||
Revision as of 14:41, 9 April 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 Test writer.
- QA Team Roles
- QA TODO list
- QA Team members
- QA events
- OpenVZ bug control
- QA Team hardware
- Follow News/updates
- Contacts
Useful articles
- Reporting OpenVZ problem
- Known problems
- Kernel debug options
- When you have an oops
- Kernel versioning
- SysRq debugger
- Magic SysRq Key
- Stracing a program
- Processes in D state
- Remote console setup
- Hardware testing
External links
- 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
