Results 1 to 3 of 3

Thread: Starting the event recorder after having executed tests

  1. #1

    Default Answered: Starting the event recorder after having executed tests

    Opening up the event recorder anywhere inside the it-Blocks causes the program to immeadiately start recording after the page is loaded and not execute the tests, or even the code that was written before the line where the recorder was started, first. Same goes for the inspect tool.

    Code inside the beforeAll-method is executed though.

    Is there a way around this or is this behaviour intentionally?

  2. When launching the Event Recorder, it will execute any code within the current test/spec only (the current "it" block), up to the line where you placed the cursor within the individual test. After that, the Event Recorder will start monitoring for browser interactions.

    If you need the Event Recorder to execute code in prior tests, then the logic from those prior tests needs to either be placed inside of a "beforeAll" / "beforeEach", or inside the individual test/spec from where the Event Recorder was launched.

  3. #2
    Sencha - Sales Team daniel.gallo's Avatar
    Join Date
    Apr 2009
    Location
    Redwood City, CA
    Posts
    338
    Answers
    55

    Default

    When launching the Event Recorder, it will execute any code within the current test/spec only (the current "it" block), up to the line where you placed the cursor within the individual test. After that, the Event Recorder will start monitoring for browser interactions.

    If you need the Event Recorder to execute code in prior tests, then the logic from those prior tests needs to either be placed inside of a "beforeAll" / "beforeEach", or inside the individual test/spec from where the Event Recorder was launched.
    Daniel Gallo
    Senior Solutions Architect
    Sencha Inc.

  4. #3
    Sencha - Sales Team daniel.gallo's Avatar
    Join Date
    Apr 2009
    Location
    Redwood City, CA
    Posts
    338
    Answers
    55

    Default

    The same is also true for the Inspect tool.

    However, you can temporarily disable highlighting mode with the Inspect tool either by toggling the "Highlighting On" button in the Inspect screen, or by pressing Ctrl + I on the keyboard when the browser window has focus. This enables you to temporarily interact with the app to show a particular screen, then resume Inspect mode by clicking the Highlighting button or pressing Ctrl + I on the keyboard again.
    Daniel Gallo
    Senior Solutions Architect
    Sencha Inc.

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
  •