Closed Bug 1470450 Opened 2 years ago Closed 2 years ago

Add a debug mode to raptor


(Testing :: Raptor, enhancement)

Version 3
Not set


(firefox65 fixed)

Tracking Status
firefox65 --- fixed


(Reporter: rwood, Assigned: rwood)




(1 file)

If there's some kind of web extension error (i.e. code syntax, or a webext API has broken) raptor will just timeout awaiting the pageload, and there are no error messages in the raptor console/production log.

We need a way to capture js errors in the webext itself (i.e. webext errors that are dumped to the js web console) and dump them to the terminal/production logs.
Blocks: 1473078
Summary: Caputure raptor webext js console errors → Capture raptor webext js console errors
We definitely need this, without it, to debug the raptor webext you need to:

- hack the control_server code to not shutdown the browser
- hack the raptor webext runner code to not close the browser tab

Then run raptor - during the 30 second startup pause, go to about:debugging, turn on webext debugging, and choose to debug the Raptor webext (window pops up, choose console). That will display console output for the main raptor runner.js

Then when the pageload test starts (a new tab is opened and page is loaded), open the web console for that page (that will display console output from the raptor measure.js content) 

We need a debug mode that captures the console from runner.js and measure.js and dumps to terminal.
Note, when running raptor on android geckoview the webext console.log statements already appear in the adb logcat; as :bc noted on irc we should pull those into the main logging (not sure how).

When running on Desktop not sure how to get the web ext console.log statements or if that's possible.
See Also: → 1491114
I don't see a way to do this. Although if we add a debug mode, we can startup Firefox with the browser console open, that will display the console.log messages there from the raptor web extension.

Use this bug to implement a debug mode for raptor that will at least:

- get rid of the 30 second browser init pause
- set pagecycles to 1
- open browser console on launch
Summary: Capture raptor webext js console errors → Add a debug mode to raptor
Depends on: 1501809
One way to get console.log messages out of the raptor webext and into the terminal/logs:

Inside the raptor webext js, instead of console.log, use a wrapper function that:

- accepts the string to log;
- dumps the string to console.log;
- adds the string to a growing list of strings already logged

Then in the webext cleanup (or at a timeout) send the list of console strings to the raptor control server; and have the raptor control server dunp it to terminal. Something like that may work.
Assignee: nobody → rwood
Sweet, starting Firefox with '-jsconsole' opens the browser console; and all the console.log messages from both the main raptor runner as well as the measure.js content are printed there. No need to capture the console.log errors for the control server/terminal.
I also added a section about debug-mode to the Raptor wiki:
Pushed by
Add a debug mode to raptor; r=jmaher
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Blocks: 1509381
You need to log in before you can comment on or make changes to this bug.