Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Issue about legacy selenium test cases on RadioItem

    Hi,

    We observe an issue for selenium test on RadioItem . We have many legacy test cases for RadioItems which are recorded on SmartClient 8.x. They work well on SmartClient_v91p_2015-02-17_PowerEdition but fail on SmartClient_v91p_2016-01-09_PowerEdition.

    For example, while trying the following standalone in the feature explorer,
    Code:
    isc.DynamicForm.create({
    ID: "RGI",
    width: 300,
    fields: [{name: "testRG", type:"radioGroup", valueMap:{"NT":"Navigation Tree", "MT": "Miller Table"}, defaultValue: "NT", vertical: false}]
    })

    On both v91p_2015-02-17 and v91p_2016-01-19, the locator recorded by selenium IDE for the first Radio Item "NT" is
    Code:
    "scLocator=//testRoot[]/child[Class=DynamicForm||index=0||length=1||classIndex=0||classLength=1]/item[name=testRG||title=testRG||value=NT||index=0||Class=RadioGroupItem]/item[title=Navigation%20Tree||value=NT||index=0||Class=RadioItem]/element"

    However, in the legacy locator we currently have, there's an extra "name" property in the item block for Radio Item, it looks like
    Code:
    "scLocator=//testRoot[]/child[Class=DynamicForm||index=0||length=1||classIndex=0||classLength=1]/item[name=testRG||title=testRG||value=NT||index=0||Class=RadioGroupItem]/item[name=%24540NT||title=Navigation%20Tree||value=NT||index=0||Class=RadioItem]/element".

    While trying the legacy locator by isc.AutoTest.getElement() on SmartClient_v91p_2015-02-17_PowerEdition it can get the correct element, but on SmartClient_v91p_2016-01-09_PowerEdition nothing is found.
    Code:
    "isc.AutoTest.getElement("//testRoot[]/child[Class=DynamicForm||index=0||length=1||classIndex=0||classLength=1]/item[name=testRG||title=testRG||value=NT||index=0||Class=RadioGroupItem]/item[name=%24540NT||title=Navigation%20Tree||value=NT||index=0||Class=RadioItem]/element")"
    Thanks,
    Robin

    #2
    We're looking into the cause and will update this thread shortly. If you try a release dated 12-18-2015 or earlier that may avoid this issue.

    Comment


      #3
      This should be fixed in the latest builds (for SC 9.1p, the ones stamped 2016-01-16). If for some reason the issue persists, please let us know.

      Comment

      Working...
      X