You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm struggling to find a way to assert that the debugger stops on an exception and writes to stderr when continued. Here's what I want to write:
awaitPromise.all([dc.configurationSequence(),dc.launch(config),dc.assertOutput("stderr","Test failed. See exception logs above."),dc.assertStoppedLocation("exception",{line: positionOf("// EXCEPTION").line,path: flutterTestBrokenFile.fsPath,}),]);
The problem is, the stderr is only written after the user hits continue. I thought I just chain a .then((_) => dc.continueRequest(...) request onto the end of the the assertStoppedLocation but it needs a threadId which is used inside assertStoppedLocation but not exposed in any way.
Is it possible to add an option to allow assertStoppedLocation to resume (or exposed the thread ID, but that may be tricky since it's returning a StackTrace response which doesn't contain it).
The text was updated successfully, but these errors were encountered:
I'm struggling to find a way to assert that the debugger stops on an exception and writes to stderr when continued. Here's what I want to write:
The problem is, the
stderr
is only written after the user hits continue. I thought I just chain a.then((_) => dc.continueRequest(...)
request onto the end of the theassertStoppedLocation
but it needs athreadId
which is used insideassertStoppedLocation
but not exposed in any way.Is it possible to add an option to allow
assertStoppedLocation
to resume (or exposed the thread ID, but that may be tricky since it's returning a StackTrace response which doesn't contain it).The text was updated successfully, but these errors were encountered: