FYI, for now a workaround that works is to create another test that simply call this the parametrized test and set the tag on that new test.
However i think that this is a bug.
FYI, for now a workaround that works is to create another test that simply call this the parametrized test and set the tag on that new test.
However i think that this is a bug.
Hi,
Sorry for the late jumping in...
I do not think that this is a bug and would treat it as expected behavior.
The reason is that Execution Plan and execution by tag are separate unrelated entities. It is possible to add the same script routine/keyword test into Execution Plan more than once as separate tests and provide different parameter values for every entry. Also, Execution Plan may not contain test entry for some script routine/keyword test but this script routine/keyword test still can be called and executed by tag.
You can still use your current approach with the wrapper that calls your test with expected parameter value. If it is possible to provide default value for the optional parameter, you can also set default value to some obviously incorrect value (say, to -2 (minus two) and then, at the start of the test check parameter's value. If it equals to -2 then set it to the value that you need (this means that test was called by tag) and leave it as it is otherwise (which means test was called from Execution Plan).
Another technique that might work is to check in your test if TestItems.Current object exists. If it does, this means that your test was called from Execution Plan. See https://support.smartbear.com/testcomplete/docs/reference/project-objects/project/testitems/current.html for more details.
Well thats the thing.
Unless i missunderstood, with the approach you have suggested (to put the default value to -2) it would not work if run by the tag. That value would be nothing and therefore treated as 0.
My test does have a default value defined for the parameter. But when ran through the tag, that parameter is "ignored" and set to nothing.
> My test does have a default value defined for the parameter.
Can you show how default value for the test parameter is defined? (Not how the value for the parameter is provided in the Execution Plan, but how it is defined in the test itself?)
Sure thing.
Please note that i've also provided an example project, which ill reattach) that replicates the issue (if it is an issue 😃)
