Difference between revisions of "Tester"
(Replace feature list by link to QA TODO) |
m (rm double empty lines) |
||
| Line 16: | Line 16: | ||
See OpenVZ features requires testing in [[QA TODO list|QA TODO list]]. | See OpenVZ features requires testing in [[QA TODO list|QA TODO list]]. | ||
| − | |||
=== OpenVZ OS template === | === OpenVZ OS template === | ||
| − | |||
We release OS templates as soon as new version of appropriate Linux distro is available. New OS templates announced on [https://openvz.org/News/updates#Templates_update_January_2015 wiki]. Follow these steps to validate new OS template: | We release OS templates as soon as new version of appropriate Linux distro is available. New OS templates announced on [https://openvz.org/News/updates#Templates_update_January_2015 wiki]. Follow these steps to validate new OS template: | ||
| Line 26: | Line 24: | ||
* create cache for it | * create cache for it | ||
* create container based on that OS template | * create container based on that OS template | ||
| − | |||
== Bug validation == | == Bug validation == | ||
Revision as of 22:11, 11 March 2015
Contents
Setting up a test environment
- setup Linux distributive (RPM based distro is preferred) on one of your test hardware node
- follow OpenVZ installation instructions
- install component which you want to test
- please consider to setup logging console. Especially you want to test new versions of OpenVZ kernel.
- add configuration of your hardware node to the wiki table
Exploratory testing
With an installed version of the development release up and running, you can perform exploratory testing against any packages of components you wish. Go wild! Try and break things! See if the new software can handle the unexpected, or even the normal use cases. If you find a bug, report it!
OpenVZ kernel
Sometimes new version of OpenVZ kernel contains new feature. Usually we provide howto described steps to enable feature and shortest steps how to use it.
See OpenVZ features requires testing in QA TODO list.
OpenVZ OS template
We release OS templates as soon as new version of appropriate Linux distro is available. New OS templates announced on wiki. Follow these steps to validate new OS template:
- download new OS template
- create cache for it
- create container based on that OS template
Bug validation
In each release we do our best to fix as much bugs as possible. You can help us with validation of bugs fixed in latest version.
- open changelog of component in News (see as example ploop-1.12.2)
- find numbers of bugs fixed in that version
- try to reproduce each bug on your test environment and keep appropriate comment in OpenVZ bugzilla about results
