[
https://issues.apache.org/jira/browse/AMBARI-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933445#comment-14933445
]
Hudson commented on AMBARI-13257:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3551 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3551/])
AMBARI-13257 Assign unique id/class to database selection radio
buttons/pulldowns. (ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f67543c406be7d014c3c35c1c572f6ff501241be)
* ambari-web/app/templates/wizard/controls_service_config_radio_buttons.hbs
* ambari-web/test/views/common/controls_view_test.js
* ambari-web/app/views/common/controls_view.js
> Assign unique id/class to database selection radio buttons/pulldowns
> --------------------------------------------------------------------
>
> Key: AMBARI-13257
> URL: https://issues.apache.org/jira/browse/AMBARI-13257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.2
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13257.patch
>
>
> The database type selection radio buttons / pulldowns need to have stable IDs
> or classes, such as:
> class=“MYSQL”
> class=“ORACLE”
> class=“SQLA”
> etc.
> This would make automated tests immune against label changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
