Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow continuing from assertStoppedLocation #174

Open
DanTup opened this issue Apr 17, 2018 · 0 comments
Open

Allow continuing from assertStoppedLocation #174

DanTup opened this issue Apr 17, 2018 · 0 comments
Labels
feature-request Request for new features or functionality
Milestone

Comments

@DanTup
Copy link

DanTup commented Apr 17, 2018

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:

await Promise.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).

@weinand weinand self-assigned this May 10, 2018
@weinand weinand added the feature-request Request for new features or functionality label Oct 19, 2021
@weinand weinand added this to the On Deck milestone Oct 19, 2021
@weinand weinand removed their assignment Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants