Details

    • Type: Bug Fix
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      AFT Step: By.xpath: //input[@name='methodToCall.performLookup.(!!org.kuali.rice.kew.doctype.bo.DocumentType!!).(((name:document.newMaintainableObject.parentDocType.name,documentTypeId:document.newMaintainableObject.docTypeParentId,))).((`document.newMaintainableObject.parentDocType.name:name,`)).((<>)).(([])).((**)).((^^)).((&&)).((//)).((~~)).(::::;http://env2.rice.kuali.org/kr/lookup.do;::::).anchor4'] no such element
        (Session info: chrome=43.0.2357.130)
        (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 30.03 seconds
      For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
      

      This error is caused by the Java 8 upgrade which causes the order of the property map to be different.

        Attachments

          Activity

          cniesen Claus Niesen created issue -
          cniesen Claus Niesen made changes -
          Field Original Value New Value
          Assignee Claus Niesen [ cniesen ]
          ewestfal Eric Westfall made changes -
          Labels LongTerm

            People

            • Assignee:
              Unassigned
              Reporter:
              cniesen Claus Niesen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: