1. #1
    Sencha User
    Join Date
    Jul 2012
    Posts
    2
    Vote Rating
    0
    bmiddlebrook is on a distinguished road

      0  

    Default Unanswered: Sencha Touch 2 and Selenium

    Unanswered: Sencha Touch 2 and Selenium


    Hi,

    I've been trying to automate a sencha touch 2 implementation with selenium via the Chrome browser on a Pc. Is anyone else doing this with success?

    I've run into an issue where Selenium is throwing a NoSuchElement exception when trying to find a button on a x-msgbox. Does anybody have a solution on how to make WebDriver recognize the msgbox?

    Thanks in advance.

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    37,074
    Answers
    3500
    Vote Rating
    854
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Are you sure it's rendered at the time the test fires?
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha User
    Join Date
    Jul 2012
    Posts
    2
    Vote Rating
    0
    bmiddlebrook is on a distinguished road

      0  

    Default


    I am sure the web element was rendered when the test fired. Dev changed something, the xpath changed, and selenium now recognizes the button. I am trying to get to the bottom of what was changed and will post if I figure out what change resulted in selenium now recognizing it.

Thread Participants: 1

Tags for this Thread