Forum Discussion
AlexKaras
14 years agoChampion Level 3
Hi Tomer,
> This is the command line I invoke on the Test Execute machine:
> C:\Test_complete_proj\VSS_1\VSS_1.pjs /r /p:VSS_1 /u:vss_script_1 /rt:main view_directory_listing \\\\10.1.1.149\\dev
The case is that you are not calling main() routine with two parameters, but start TestExecute with commend line that contains a set of parameters. Some of these parameters are processed by TestExecute (like /r, /p, etc.) but some are not (like view_directory_listing and \\\\10.1.1.149\\dev).
So in your test code you should get command line used to start the test, parse it for parameters and perform actions depending on the passed parameters. See "TestComplete command line parameters" help topic for more details.
> My background is in C [...]
The above exactly corresponds with the behavior of the ordinary C program - the main() function gets the list of command line arguments that should be processed within main() and reacted accordingly.
> This is the command line I invoke on the Test Execute machine:
> C:\Test_complete_proj\VSS_1\VSS_1.pjs /r /p:VSS_1 /u:vss_script_1 /rt:main view_directory_listing \\\\10.1.1.149\\dev
The case is that you are not calling main() routine with two parameters, but start TestExecute with commend line that contains a set of parameters. Some of these parameters are processed by TestExecute (like /r, /p, etc.) but some are not (like view_directory_listing and \\\\10.1.1.149\\dev).
So in your test code you should get command line used to start the test, parse it for parameters and perform actions depending on the passed parameters. See "TestComplete command line parameters" help topic for more details.
> My background is in C [...]
The above exactly corresponds with the behavior of the ordinary C program - the main() function gets the list of command line arguments that should be processed within main() and reacted accordingly.
Related Content
Recent Discussions
- 3 days agoMW_Didata