Skip to content

Conversation

@jonahwilliams
Copy link
Contributor

@jonahwilliams jonahwilliams commented Jun 3, 2021

Ensure that devtools will launch from the cmdline on a profile build

WIP due to testing

@flutter-dashboard flutter-dashboard bot added the framework flutter/packages/flutter repository. See also f: labels. label Jun 3, 2021
@google-cla google-cla bot added the cla: yes label Jun 3, 2021
@jonahwilliams
Copy link
Contributor Author

FYI @Hixie .

@Hixie
Copy link
Contributor

Hixie commented Jun 3, 2021

Oh, haha, good catch.

@jonahwilliams
Copy link
Contributor Author

I'd like to find a way to test this without adding a devicelab test, but I'm scratching my head a bit right now

);

registerStringServiceExtension(
name: 'activeDevToolsServerAddress',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one probably needs to move out of the assert block too right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh good catch

@jonahwilliams
Copy link
Contributor Author

Soliciting testing ideas:

I can't turn off asserts in our unit tests, so I can't show that the extension is still registered.
I can't run a profile build in the tool integration tests, the flutter_tester only supports debug
I could add a new devicelab test to verify devtools connects, but sometimes devtools fails to activate on CI and I'm certain this would be flaky.

@Hixie
Copy link
Contributor

Hixie commented Jun 3, 2021

I can't think of a way to really test this other than an end-to-end test in devicelab either.

@Hixie
Copy link
Contributor

Hixie commented Jun 3, 2021

Maybe the first step is to fix the flakiness. :-)

(In the meantime you could also make the test pass in the case where it fails to bootstrap devtools, since we already test that in existing tests. Can a test decide midway through itself that it should be skipped?)

@jonahwilliams
Copy link
Contributor Author

Yeah, I think that's what we have to do. if its flaky we can revisit.

@jonahwilliams jonahwilliams marked this pull request as ready for review June 3, 2021 21:54
@flutter-dashboard flutter-dashboard bot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Jun 3, 2021
@jonahwilliams
Copy link
Contributor Author

I added a devicelab test, will add to infra config after this lands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. framework flutter/packages/flutter repository. See also f: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants