fune/devtools/server/tests/xpcshell/test_frameactor-03.js
Alexandre Poirot c29b020b4a Bug 1571212 - [devtools] Wait for resume to complete in all xpcshell tests. r=bomsy
test_stepping-12.js wasn't correctly waiting for thread to be resumed between each of its sub test.

Similarly, other tests weren't waiting for thread front's resume request to be resume.
I'm also spreading the usage of resumeAndWaitForPause to better ensure we resume and wait for next paused event
without any race condition. Listening to "paused" after calling "resume" is subject to race conditions.

Differential Revision: https://phabricator.services.mozilla.com/D136125
2022-01-19 17:43:00 +00:00

54 lines
1.3 KiB
JavaScript

/* Any copyright is dedicated to the Public Domain.
http://creativecommons.org/publicdomain/zero/1.0/ */
"use strict";
/**
* Verify that a frame actor is properly expired when the frame goes away.
*/
add_task(
threadFrontTest(async ({ threadFront, debuggee }) => {
const packet = await executeOnNextTickAndWaitForPause(
() => evalCode(debuggee),
threadFront
);
const frameActorID = packet.frame.actorID;
{
const { frames } = await threadFront.getFrames(0, null);
ok(
frames.some(f => f.actorID === frameActorID),
"The paused frame is returned by getFrames"
);
Assert.equal(frames.length, 3, "Thread front has 3 frames");
}
await resumeAndWaitForPause(threadFront);
await checkFramesLength(threadFront, 2);
{
const { frames } = await threadFront.getFrames(0, null);
ok(
!frames.some(f => f.actorID === frameActorID),
"The paused frame is no longer returned by getFrames"
);
Assert.equal(frames.length, 2, "Thread front has 2 frames");
}
await threadFront.resume();
})
);
function evalCode(debuggee) {
debuggee.eval(
"(" +
function() {
function stopMe() {
debugger;
}
stopMe();
debugger;
} +
")()"
);
}