Editing Tester

== Setting up a test environment ==

* setup Linux distribution (RPM based distro is preferred) on one of your [[QA Team hardware|test hardware node]]
* follow OpenVZ [[quick installation]] guide
* install component which you want to test
* please consider setting up [[Remote console setup|logging console]], especially if you want to test new versions of OpenVZ kernel.
* add configuration of your hardware node to the [[QA Team hardware]] page

== 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 found a bug, report it as described at [[reporting OpenVZ problem]]!

=== OpenVZ kernel ===

Sometimes a new version of the OpenVZ kernel contains a new feature. Usually we provide a howto describing steps to enable and use the feature.

See OpenVZ features requires testing in [[QA TODO list]].

=== OpenVZ OS template ===

We release a new OS template as soon as new version of appropriate Linux distro is available. New OS templates are announced at [[News/updates]] page and on the [https://lists.openvz.org/mailman/listinfo/announce announce@ mailing list].

Follow these steps to validate new OS template:

* download new OS template (you can use {{Man|vztmpl-dl|8}} tool for that)
* create a 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.

* read through the changelog of the component (for a changelog example, see [[Download/ploop/1.12.2]])
* find IDs of bugs fixed in that version
* try to reproduce each bug on your test environment and let us know your results by adding a comment to the appropriate bug entry in https://bugzilla.openvz.org/

[[Category: QA]]