Editing Tester

Jump to: navigation, search

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 distribution (RPM based distro is preferred) on one of your [[QA Team hardware|test hardware node]]
+
* setup Linux distributive (RPM based distro is preferred) on one of your [[QA Team hardware|test hardware node]]
* follow OpenVZ [[quick installation]] guide
+
* follow OpenVZ [[Quick_installation|installation instructions]]
 
* install component which you want to test
 
* 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.
+
* 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 [[QA Team hardware]] page
+
* 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 found a bug, report it as described at [[reporting OpenVZ problem]]!
+
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 a new version of the OpenVZ kernel contains a new feature. Usually we provide a howto describing steps to enable and use the feature.
+
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|QA TODO list]].
  
See OpenVZ features requires testing in [[QA TODO list]].
 
  
 
=== OpenVZ OS template ===
 
=== 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:
+
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
  
* download new OS template (you can use {{Man|vztmpl-dl|8}} tool for that)
 
* create a container based on that OS template
 
  
 
== Bug validation ==
 
== Bug validation ==
Line 30: Line 32:
 
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.
  
* read through the changelog of the component (for a changelog example, see [[Download/ploop/1.12.2]])
+
* 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 IDs of bugs fixed in that version
+
* find numbers 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://bugs.openvz.org/
+
* try to reproduce each bug on your test environment and keep appropriate comment in OpenVZ bugzilla about results
  
 
[[Category: QA]]
 
[[Category: QA]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: