Bug 1581963 - [devtools] Handle errors properly when capturing a profile r=profiler-reviewers,mstange

Differential Revision: https://phabricator.services.mozilla.com/D245886
This commit is contained in:
Julien Wajsberg
2025-05-22 16:26:42 +00:00
committed by jwajsberg@mozilla.com
parent 2417113533
commit 29c9a8dba5
5 changed files with 61 additions and 11 deletions

View File

@@ -78,7 +78,26 @@ add_task(async function () {
"The profiler was stopped and the profile discarded."
);
// Clean up.
await front.destroy();
await client.close();
});
add_task(async function test_error_case() {
const { front, client } = await initPerfFront();
try {
// We try to get the profile without starting the profiler first. This should
// trigger an error in the our C++ code.
await front.getProfileAndStopProfiler();
ok(false, "Getting the profile should fail");
} catch (e) {
Assert.stringContains(
e.message,
"The profiler is not active.",
"The error contains the expected error message."
);
}
await front.destroy();
await client.close();
});