hcimvf
Note: The related script hcimvf is located under
$hciroot/bin.
hcimvf (Migration Validation Framework) is a regression testing tool that automatically processes SMAT file/Database and gets route test outputs. This tool can also compare two test outputs.
hcimvf -testid value -smatfile value [-smatdbkey value]
[-obsmatdbkey value] [-smatencoding value] -thread value [-verbose] [-output value]
-testid value
specifies the test ID.-smatfile value
specifies full-path of SMAT file. Only one file is supported. Database SMAT must end with .smatdb.[-smatdbkey value]
specifies the SMAT Database key. This is treated as unencrypted if not specified or empty.[-obsmatdbkey value]
specifies the outbound encryption key. This is treated as unencrypted if not specified or empty.[-smatencoding value]
specifies the encoding of message content. The default is UTF-8.-thread value
specifies the thread name to do the route test.[-verbose]
specifies logging in verbose format.[-output value]
specifies the full path for the output file.The default is $HCISITEDIR/exec/hcimvf/testid/output/testid.sqlite.
Or
hcimvf -testid value -old value [-oldkey value]
-new value [-newkey value] [-verbose] [-output value]
-testid
value specifies the test ID.-old
value specifies the full path of the old test output file.[-oldkey value]
specifies the encryption key for the old test output file.-new value
specifies the full path of the old test output file.[-newkey value]
specifies the encryption key for the new test output file.[-verbose]
specifies logging in verbose format.[-output value]
specifies the full path for the output file.The default is $HCISITEDIR/exec/hcimvf/testid/output/output.rpt.
Notes
hcimvf works when copying to the 19.1 and 6.2 versions. To do this:
- Copy $HCIROOT/bin/hcimvf* to the lower version under the same directory.
- Modify the first line of the script with the current root name.
- After invoking hcimvf,
testid dir
is created under $HCISITEDIR/exec/. The log, status, and output are located in this directory.
Command limitation: When two test outputs are compared and are different, the source message cannot be located; only the batch that contains the source message can be located.
Limitation example:
- The routed message identifier is:
$ibthread-$batchIndex-$obthread-$msgIndex
. batchIndex
is used for performance considerations.- The batch number is 1000.
- hcimvf invokes hciroutetest, but cannot back trace if batch messages are used as input.
- Example:
- Process SMAT Database and get the route test output. Example:
hcimvf -testid test_route -smatfile c:/cloverleaf/cis20.1/integrator/t-hcimvf/exec/processes/ multiple_route/ib.smatdb -smatdbkey t-hcimvf -obsmatdbkey t-hcimvf -thread src
- Compare two test outputs:
hcimvf -testid test_diff -old c:/cloverleaf/cis20.1/integrator/t-hcimvf/exec/hcimvf/cmp1/output/ cmp1.sqlite -oldkey t-hcimvf -new c:/cloverleaf/cis20.1/integrator/t-hcimvf/exec/hcimvf/cmp2/output/ cmp2.sqlite -newkey t-hcimvf
Note: File SMAT does not include .msg or .idx.
- Process SMAT Database and get the route test output. Example: