Andrii Tkach created AMBARI-23401:
-------------------------------------
Summary: Problems while selecting the property uniquely in
Configurations screen while installation
Key: AMBARI-23401
URL: https://issues.apache.org/jira/browse/AMBARI-23401
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.0
While scripting the automation code for the new UI installer, could not select
some properties uniquely and some problems faced:
# Unable to select some properties by their label in xpath:
{panel}
* In Advanced zeppelin-config panel under Zeppelin configurations, there are a
bunch of configurations related to zeppelin.ssl. As seen in screenshot-1, all
the labels have zeppelin.ssl in them and if one were to type textbox with label
zeppelin.ssl using XPATH strict text match, i.e. //*[text()=’zeppelin.ssl’], it
fails. This is because within the label there are some html elements (see
screenshot-1) like <wbr> which do not allow a strict match to the label.
* A simple workaround would be to use xpath contains() operator, but it would
return multiple fields for the same label, which is not good.
{panel}
# Try to select the property by ‘data-qa’ also has similar problems to above
{panel}
As per screenshot-2, the data-qa attribute has the value
‘service-config-zeppelin-ssl-zeppelin-config-xml-default’ which can only be
covered by xpath //*[contains(@data-qa,’zeppelin-ssl’)]. But this would again
lead to multiple matches in the UI.
{panel}
Two asks from a test automation point of view:
# Remove any HTML entity from in between the label text
{panel}
Example: zeppelin.<wbr>ssl to zeppelin.ssl
{panel}
# Set the data-qa attribute for the input fields to just the property name as
specified in Blueprint. For example, if the Blueprint property is
‘zeppelin.ssl’, the data-qa attribute can be ‘zeppelin-ssl’.
This would enable the automation code to uniquely identify the property fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
