| || |
QC to WR Test Parms Length and Use of Spaces
I have a WR script that I execute from Quality Center 9 which has six parameters in it. The last parameter is basically the name of a radio button that the script will select when the dialog box it is on appears. The value of the parameter is 26 characters long and includes spaces. What I have found is I can run this test normally from WinRunner, setting default values for the parameters, including the long parameter value described above. When run from QC, however, the script begins to load, then immediately terminates with a status of "Finished". No error message is returned and the test does not even generate a report.
I threw together a quick one statement test and passed two parms to it, both of which had spaces. If the length of the parm was 14 characters or less, the test ran normally. 15 or more characters and an immediate termination was the result.
Does anyone know of a limitation to the length of a test parm that can be passed from QC to WR and whether the presence of spaces can be an issue? Thanks.
Re: QC to WR Test Parms Length and Use of Spaces
Better contact the Mercury Support using a SR