Description
In our automated CI tests we recently had the problem that when a testcase name contains a colon : the testcase parameters from the commandline will not be passed into the testcase. This seems to be a bug in the design of the CLI syntax.
/tcpa|testcaseparam|testcontainerparam:<test container>:<parameter name>=<value>
For example testcase name Common:TestA
/tcpa:Common:TestA:param1=value1
Maybe the colon should be forbidden in the RanorexSudio GUI when naming a testcase, some sort of reserved character like the whitespace char?
Enviroment:
Win10 20H2
Ranorex: all versions
Colon in testCaseName breaks commandLineParameters
Re: Colon in testCaseName breaks commandLineParameters
Hi,
Well, to be quite honest, using colon character in test case/smart folder (any) name is a pretty uncommon thing. In fact, it's so uncommon that nobody in Rx design team probably even considered the need of forbidding such special character I would not consider it a bug, just a bad side effect of pretty uncommon use case. I would suggest to use 'underscore' instead of colon, space or anything else.
Well, to be quite honest, using colon character in test case/smart folder (any) name is a pretty uncommon thing. In fact, it's so uncommon that nobody in Rx design team probably even considered the need of forbidding such special character I would not consider it a bug, just a bad side effect of pretty uncommon use case. I would suggest to use 'underscore' instead of colon, space or anything else.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration