After looking at it. The integration tests don't work with engine changes in the same PR - so it seems like they need to be a follow-on PR: #179772

I think you can make engine changes and framework changes in the same pr. What I dont think you can do is add a ci target and run it in presubmit.

Maybe add the target in a parallel pr and make it always passing then modify it in this pr?

I think you can make engine changes and framework changes in the same pr. What I dont think you can do is add a ci target and run it in presubmit.

Maybe add the target in a parallel pr and make it always passing then modify it in this pr?

I made an integration test to check for the bug that was caused by the initial PR: #179902

However, this is not an add-to-app that actually checks to see if content sizing correctly works. That integration test is here: #179772

The way the flutter build is run, it does not necessarily use local engine changes (unless it's doing something in the background). I admit it wouldn't be a good test unless it actually did use local engine changes. That said, when I run it locally, it does not. Hopefully CI is smarter than that.

Confirmed that the new integration test passes:

00:02 �[32m+0�[0m: Should be able to hide and show platform view multiple times�[0m
D/ProfileInstaller( 7529): Installing profile for com.example.android_engine_test
Updating golden file: android_engine_test.opengles.hide_show_hide_platform_view.png (22918 bytes)...
Skia Gold comparison succeeded comparing "android_engine_test.opengles.hide_show_hide_platform_view.png".
00:05 �[32m+1�[0m: (tearDownAll)�[0m
00:05 �[32m+1�[0m: All tests passed!�[0m