KVM-Autotest-Docs: Difference between revisions
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
== How to use == | == How to use == | ||
It's very simple for you to use the command line, suppose you are in the directory of kvm subtest, you can pass test parameters through: | |||
../../bin/autotest control --args="key1=value1 key2=value2 ...... keyN=valueN" | |||
KVM-Autotest supports two kinds of parameters: | |||
# keywords "only" and "no": they serve as the same function as in configuration file, limit and exclude variants. | |||
## For each "only=x", the control file would generate a "only x" and pass it to the configuration file analyzer | |||
## For each "no=y", the control would generate a "no y" and pass it to the configuration file analyzer | |||
# test parameters: all other are passed to the configuration analyzer untouched, that is to say, you could specify any test parameters by this way. | |||
== Limitations == | == Limitations == |
Revision as of 23:14, 23 January 2011
Introduction
Recent autotest supports passing test parameters to control file through --args options. This is also been introduced in kvm-autotest which can let user do some basic tests configurations (variants limitation or excluding, parameters configuration) through command line.
You should have some basic understanding of the test parameters and configuration file format before using the command line. If not, you are suggested to read the test configuration file format and test parameters before continuing.
How to use
It's very simple for you to use the command line, suppose you are in the directory of kvm subtest, you can pass test parameters through:
../../bin/autotest control --args="key1=value1 key2=value2 ...... keyN=valueN"
KVM-Autotest supports two kinds of parameters:
- keywords "only" and "no": they serve as the same function as in configuration file, limit and exclude variants.
- For each "only=x", the control file would generate a "only x" and pass it to the configuration file analyzer
- For each "no=y", the control would generate a "no y" and pass it to the configuration file analyzer
- test parameters: all other are passed to the configuration analyzer untouched, that is to say, you could specify any test parameters by this way.