Results 1 to 2 of 2

Thread: Sencha Test 2.0.0.287 : How to see the failure reason ?

  1. #1
    Sencha User
    Join Date
    Nov 2016
    Posts
    7

    Default Sencha Test 2.0.0.287 : How to see the failure reason ?

    Used the Event Recorder to record a simple test that logged into to an application, and navigated through two layers of a hierarchy
    ST.play([
    { type: "tap", target: "component[itemId="loginAsUserLink"]", x: 95, y: 13 },
    { type: "type", target: "textfield[name="user_name"] => input", text: "", caret: 0 },
    { type: "keydown", target: "textfield[name="user_name"] => input", key: "Tab", caret: 5 },
    { type: "keyup", target: "textfield[name="login_password"] => input", key: "Tab", caret: 0 },
    { type: "type", target: "textfield[name="login_password"] => input", text: "", caret: 0 },
    { type: "type", target: "textfield[name="login_password"] => input", text: "", caret: 3 },
    { type: "tap", target: "button[itemId="loginBtn"]", x: 119, y: 29 },
    { type: "tap", target: "glass-base-view-appmanager-categories => [data-recordindex="11"]", x: 54, y: 67 },
    { type: "mousedown", target: "glass-base-view-appmanager-apps[reference="appView"] => [data-recordindex="4"]", x: 24, y: 10, detail: 1 },
    { type: "mouseup", target: "glass-base-view-appmanager-apps[reference="appView"] => [data-recordindex="4"]", x: 24, y: 67, detail: 1 },
    { type: "click", target: "glass-base-view-appmanager-apps[reference="appView"] => [data-recordindex="4"]", x: 24, y: 67, detail: 1 }


    The (Chrome) browser window shut after the first selection of "glass-base-view-appmanager-categories", and the Unit Tests tab showed a single red "1". However nothing is logged to the Log panel, and double clicking on the failure count does nothing. Should I be running the test in Debug mode until it is stable ?

  2. #2
    Sencha User
    Join Date
    Jun 2015
    Location
    Ostrava, Czech republic
    Posts
    52

    Default

    Hi TABen!
    Thanks for reports what you filled!

    Debug mode and normal run - differences is that Debug mode stops on key word "debugger" in code, so you can see variables, go step by step in code etc. Normal run ignores "debugger" and just run a test. So if you haven't this word in code, it is better execute Normal run. Is it clearer?

    And for showing a error message, you need open node and then click on red cross ( X ) and then ST shows you error.

    Feel free to contact me any time
    Vojtěch Červený

Similar Threads

  1. Replies: 1
    Last Post: 9 Aug 2016, 3:46 AM
  2. Replies: 2
    Last Post: 4 Aug 2016, 4:27 AM
  3. Replies: 2
    Last Post: 2 Aug 2016, 7:31 PM
  4. Replies: 3
    Last Post: 29 Oct 2010, 11:51 PM
  5. doExtAjaxCall failure unknow reason
    By Gopal Patil in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 2 Oct 2009, 8:42 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •