Issues passing external parameter related to a dropdown menu via CLI
Environment:
All environments with CLI
OpenTAP 9.6
Steps to reproduce:
- Create new .TapPlan
- Add any step which contains a dropdown as setting (e.g. Dialog Box)
- Add the dropdown setting as "External Parameter"
- Save .TapPlan
- Execute .TapPlan via CLI passing the DropDown setting as external parameter
Actual result:
The only way to properly pass the parameter without further interaction (otherwise CLI lists options the user needs to choose from) is to provide the attribute marked in the source code.
Expected result: The user should be able to pass whatever string is visualized in the UI, not fish into the plugin code. While the CLI allows to make interactive options, it is best to avoid such behavior for highly automated environments.
Other remarks: In a similar fashion the REST-API passes back the external parameter as dropdown index.
Edited by Vivienne Spence