Forum Discussion
kso
15 years agoOccasional Contributor
it seems there is a bug in the way flags are interpreted on the command line .(at least in testexecute 7.52)
all flags placed after the /exit files are not taken into account.
by example if you place /SilentMode before /exit then tc will be excuted in silent mode
whereas in the contrary if you place /exit before /SilentMode then tc will not be executed in silent mode.
it is the same with custom flags even using ParamStr.
In the documentation, the flag /Silentmode is placed after /exit. Ther is something wrong somewhere.
TestExecute.exe [file_name] [/run
[(/project:project_name) | (/project:project_name /projectitem:item_name) |
(/project:project_name /unit:unit_name /routine:routine_name)]
[/exit] [/SilentMode]
regards,
Karim SOUAK.
all flags placed after the /exit files are not taken into account.
by example if you place /SilentMode before /exit then tc will be excuted in silent mode
whereas in the contrary if you place /exit before /SilentMode then tc will not be executed in silent mode.
it is the same with custom flags even using ParamStr.
In the documentation, the flag /Silentmode is placed after /exit. Ther is something wrong somewhere.
TestExecute.exe [file_name] [/run
[(/project:project_name) | (/project:project_name /projectitem:item_name) |
(/project:project_name /unit:unit_name /routine:routine_name)]
[/exit] [/SilentMode]
regards,
Karim SOUAK.