Parameter file not found when test case executed from Quality Center (QC)
Hi,
I am running iTest3.4. I have developed a test case has references to parameters defined in a global parameter file. I set the parameter file as global by right clicking on the param file and selecting "Set as Global". When i execute this test case from within the iTest GUI, it works fine and passed.
Now having completed the test case development, I ahve published it to Quality Center (QC). On executing the testcase from QC, the test case gets executed using "itestcli" which complains that the parameters referenced in the test case are not found.
I understand that I can manully execute the test using itestcli and pass a parameter file name using the -P command line option. But is there a way to specify global parameter file when the test case is not manully executed and instead executed from the QC test set directly??
Thanks for your help.
spanchal
Are you executing this in the exact same workspace as you had set the global parameters in? I will look into whether global parameters apply when the test case is being executed using iTestCLI.
One option would be to put the parameters into the test case or the testbed. If you had different sets of parameters, these could be handled with multiple testbeds that "referenced" one testbed.
Future releases of iTest should have support for setting parameters directly from QC, which might help. You should talk to your support/sales representatives to see when those features would be available.
In 3.4.1 and earlier releases, global parameter file is not supported when you execute a test case from QC. We have added the global parameter feature to the next release. Basically, when you publish a test case to QC, iTest will add a global parameter file url called parameterfileurl as a QC test parameter . The value is empty. User will be able to configure the global parameter file URI by going to the test instance.
Message Edited by YujieL on
09-10-2009
09:56 AM
Hi spanchal,
Global parameter file is only used in iTest GUI execution. If you are using itestcli, you have to use "--param" option and specify a URL to the parameter file.
Customers have already requested this feature and we have added support for passing in paramter file via QC which should be available in the future release.
In the meanwhile, if you are using the same workspace for most of your test executions, you could set the HPQC_ITESTCLI_ARGS environment variable to " --param "file://C:/temp/myparams.ffpt".
As a result of this, whenever itestcli is launched from HPQC, it will pass in this extra argument and you should be able to execute it similar to GUI.
Note that this is a workaround and it also means that this parameter file will be used for EVERY test case execution launched from HPQC. Normally, global parameter file should only contain parameters which can be used by any test, so this should be fine.
Another way is to have the parameters part of the testcase or testbed.
Hope this helps.
-A
Thanks for the workaround. Its good to know that the feature is already being worked upon and will be available in future release. I will live with the workaround untill that happens. Infact, it might be good to update the documentation for Parameter section to put a line mentioning this limitation and also the workaround with the env variable name. I looked at the documentation for all env variables allowed with iTest as I kind off thought there might be a varibale to specify the param file path and I could not find it in the documentation. Anyways, thanks a ton for sharing this with me.
Appreciate it !!!
Regards,
spanchal
