6,534
edits
Changes
English, internal links etc.
== Setting up a test environment ==
* setup Linux distributive distribution (RPM based distro is preferred) on one of your [[QA Team hardware|test hardware node]]* follow OpenVZ [[Quick_installation|quick installation instructions]]guide
* install component which you want to test
* please consider to setup setting up [[Remote console setup|logging console]]. Especially , especially if you want to test new versions of OpenVZ kernel.* add configuration of your hardware node to the [[QA_Team_hardware|wiki tableQA 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 find found a bug, report it as described at [[Reporting_OpenVZ_problem|report itreporting OpenVZ problem]]!
=== OpenVZ kernel ===
Sometimes a new version of the OpenVZ kernel contains a new feature. Usually we provide a howto described describing steps to enable feature and shortest steps how to use itthe feature.
See OpenVZ features requires testing in [[QA TODO list|QA TODO list]].
=== OpenVZ OS template ===
We release a new OS templates 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/Newsmailman/listinfo/updates#Templates_update_January_2015 wikiannounce announce@ mailing list]. Follow these steps to validate new OS template:
Follow these steps to validate new OS template: * download new OS template* create cache (you can use {{Man|vztmpl-dl|8}} tool for itthat)* 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.
* open read through the changelog of the component in [https://openvz.org/News/updates News] (for a changelog example, see as example [https://openvz.org/[Download/ploop/1.12.2 ploop-1.12.2]])* find numbers IDs of bugs fixed in that version* try to reproduce each bug on your test environment and keep let us know your results by adding a comment to the appropriate comment bug entry in OpenVZ https://bugzilla about results.openvz.org/
[[Category: QA]]
