You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

THIS IS A DISCUSSION DOCUMENT AND IS NOT IMPLEMENTED YET - IT WON'T WORK TODAY

There may be times that you wish to influence the tests carried out on your review. You might for example be fixing an issue that affects a particular distribution or combination of distributions, for this reason you can change the tests carried out by indicating in the commit message the changes you require.

To do this place the following comments with name value pairs in your commit message

Test-Parameters-Start:
x=y
c=e
Test-Parameters-End:

You can place more than one name value pair on a line separated by commas ie. a=b,f=g. To cater for multiple requirements we might allow for lists of requirements, which is entry being a separate test.

Test-Parameters-Start:x=y
c=e
Test-Parameters-End:
Test-Parameters-Start:
e=z,r=e
Test-Parameters-End:

The values today with permissable entries are;

Name

Description

Valid Values

ostcount

Number of OSTs to test against

1..10

clientprofile

Cobbler profile to use for clients

test

serverprofile

Cobbler profile to use for clients

test

clientdistro

Distribution to use for clients

el5, el6

serverdistro

Distribution to use for clients

el5, el6

clientarch

Architecture to use for clients

i686, x86_64

serverarch

Architecture to use for servers

i686, x86_64

nettype

Network type to use

tcp, o2ib

clientcount

Number of clients to use

2-4

no_virtualization

Set True if testing must not be virtualized

true

testgroup

Test group to test with

review, regression, quick

tests

Dot separated list of tests to run in place of a standard test group

sanity.conf_sanity.mmp etc

You do not need to specify all the values only those values important for your requirements, the test system will use your request to alter a regular test. Also to ensure that you all reviews are fully tested to a known standard the test system will run a regular unmodified testset as well as the special request.

Here is an example

LU-999 Single line description of change under 64 columns

A more detailed explanation. This can be as detailed as you'd like.
Please explain both what problem was solved and a high-level
description of how it was solved. Wrap lines at 72 columns or less.

Test-Parameters-Start:
ostcount=10,nettype=tcp
tests=conf-sanity.replay-single
Test-Parameters-End:

Signed-off-by: Random J Developer <random@developer.example.org>
Change-Id: Ica9ed1612eab0c4673dee088f8b441d806c64932
  • No labels