Now that bug 1137285 landed, inspector tests can theoretically run on luciddream via the test actor. But various still fails. Steps are: - tweak luciddream test harness to be able to run inspector tests - tweak inspector test head.js/test actor to be able to run on luciddream - enable the already passing tests - tweak tests or inspector code to get more running (Note that we won't enable all of them, as some are really specific to testing Firefox Desktop features, like "context menu->inspect" test)

WIP patch. Depends on the various patches I submitted in blocker bugs. This tweaks some tests, add luciddream.ini tests and hook head.js helpers to call luciddream ones (that, to open webide toolbox instead of browser toolbox).

Here is various small tweaks I had to do over inspector tests in order to run flawlessly on luciddream. - waiting for additional events to prevent races/pending request exceptions - use TEST_URL_ROOT, always, as file maps to different kind of URLs on luciddream - pass the window on synthesizeKey prevents easily document focus issues! - workaround the fact that the webconsole is already opened on luciddream, the webconsole-ready event is only fired on the very first time the console is opened (may be we should introduce a new event, fired any time the console is opened) - help distinguishing data: documents being used between tests (useful when something bad happens) https://treeherder.mozilla.org/#/jobs?repo=try&revision=659a122a3186

Once deps are ready, we can land that patch to enable inspector tests on luciddream.

Comment on attachment 8668479 [details] [diff] [review] various inspector tests tweaks - v1 Patrick, Here is various tweaks for inspector tests, necessary for running on luciddream. See comment 2 for more info about these tweaks. Feel free to redirect the r? to whoever makes sense!

Comment on attachment 8668479 [details] [diff] [review] various inspector tests tweaks - v1 Review of attachment 8668479 [details] [diff] [review]: ----------------------------------------------------------------- ::: devtools/client/inspector/test/browser_inspector_breadcrumbs_highlight_hover.js @@ +7,5 @@ > // Test that hovering over nodes on the breadcrumb buttons in the inspector shows the highlighter over > // those nodes > add_task(function*() { > info("Loading the test document and opening the inspector"); > + let {toolbox, inspector, testActor} = yield openInspectorForURL("data:text/html;charset=utf-8,<h1>foo1</h1><span>bar</span>"); nit: if the document content needs to be unique because this helps when tests fail, then maybe make the content something like: <h1>breadcrumbs hover test</h1><span>highlight nodes on hover</span> The benefit I see to this is that now, when people copy/paste this test to create a new one, they will see this and probably change it to match whatever their new test does.

(In reply to Patrick Brosset [:pbrosset] [:pbro] from comment #6) > The benefit I see to this is that now, when people copy/paste this test to > create a new one, they will see this and probably change it to match > whatever their new test does. Good point!

With yet another batch of inspector tests fixes, let's see how it runs on try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=be674b3adb7b Looks mostly good locally.

Waiting for try results before proceeding to review. I'm going to merge this patch with the previous one before landing, but keep it seperate for now to ease review.

Triaged as P3 for now, but since lucid dream isn't a priority anymore, we might want to close this.