Changes between Version 8 and Version 9 of WebInspectorDebugging


Ignore:
Timestamp:
Jan 11, 2018, 10:45:05 AM (7 years ago)
Author:
Joseph Pecoraro
Comment:

Remove some stale sections and mention InspectorTest.debug

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified WebInspectorDebugging

    v8 v9  
    1010defaults write com.apple.Safari WebKitDeveloperExtrasEnabled -bool YES
    1111defaults write com.apple.Safari WebKitDebugDeveloperExtrasEnabled -bool YES
    12 }}}
    13 
    14 For the Mac port, set the following defaults to allow inspecting a '''remote''' Web Inspector.
    15 
    16 
    17 {{{
    18 defaults write com.apple.WebInspector DeveloperExtrasEnabled -bool YES
    1912}}}
    2013
    … …  
    4841
    4942
    50 == Automating Reproduction/Setup Steps
    51 
    52 Often when developing a feature or fixing a bug, you need to interact with the UI to reproduce the bug or conditions where a feature is used. Rather than manually clicking UI elements over and over for every iteration, you can script these interactions to happen automatically when the Inspector opens. To do so, edit the body of `WebInspector.runBootstrapOperations()` as defined in `Source/WebInspectorUI/UserInterface/Base/Bootstrap.js`.
    53 
    54 TODO: add useful snippets here.
    55 
    56 
    5743== Using Logging inside WebInspectorUI
    5844
    … …  
    7056
    7157== Force Synchronous TestHarness Output
     58
     59Setting `InspectorTest.debug()` will log all inspector protocol traffic and `console.log` output to stderr which can be observed when the test completes or times out.
    7260
    7361Setting `InspectorTest.forceDebugLogging = true` will force all test output to be emitted via window.alert, which in a LayoutTest will add a message to test output without modifying the test page.