Editing Tester
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== Setting up a test environment == | == Setting up a test environment == | ||
− | * setup Linux | + | * setup Linux distributive (RPM based distro is preferred) on one of your [[QA Team hardware|test hardware node]] |
− | * follow OpenVZ [[ | + | * follow OpenVZ [[Quick_installation|installation instructions]] |
* install component which you want to test | * install component which you want to test | ||
− | * please consider | + | * please consider to setup [[Remote console setup|logging console]]. Especially you want to test new versions of OpenVZ kernel. |
− | * add configuration of your hardware node to the [[ | + | * add configuration of your hardware node to the [[QA_Team_hardware|wiki table]] |
== Exploratory testing == | == 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 | + | 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, [[Reporting_OpenVZ_problem|report it]]! |
=== OpenVZ kernel === | === OpenVZ kernel === | ||
− | Sometimes | + | 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. |
− | + | Features are in testing below: | |
+ | |||
+ | * [[Docker_inside_CT|Docker inside CT]] | ||
+ | * | ||
+ | |||
+ | Features are in released OpenVZ versions: | ||
+ | |||
+ | * [[IPsec|IPsec]] inside container | ||
+ | * | ||
=== OpenVZ OS template === | === OpenVZ OS template === | ||
− | |||
− | 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: |
+ | |||
+ | * download new OS template | ||
+ | * create cache for it | ||
+ | * create container based on that OS template | ||
− | |||
− | |||
== Bug validation == | == Bug validation == | ||
Line 30: | Line 39: | ||
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. | 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 [https://openvz.org/News/updates News] (see as example [https://openvz.org/Download/ploop/1.12.2 ploop-1.12.2]) |
− | * find | + | * find numbers of bugs fixed in that version |
− | * try to reproduce each bug on your test environment and | + | * try to reproduce each bug on your test environment and keep appropriate comment in OpenVZ bugzilla about results |
[[Category: QA]] | [[Category: QA]] |