Jetpack Compose 1.11 has plenty of visible UI improvements, but the testing change is the one I would put on an Android team’s upgrade checklist. Test timing assumptions are exactly the kind of thing that can turn a normal dependency bump into a confusing afternoon.
Google’s April 2026 Compose release post says version 1.11 makes the v2 testing APIs the default and deprecates the v1 APIs. The important behavioural change is the dispatcher: tests move from immediate coroutine execution with UnconfinedTestDispatcher toward queued execution with StandardTestDispatcher, where virtual time has to advance.
That is probably healthier long term. It better resembles production timing and can flush out race conditions that older tests accidentally hid. But in the short term, I would expect some tests to fail because the test was depending on immediate execution rather than a real observable state change.
I would not treat this as a random flaky-test cleanup. Put it in the upgrade plan, read the migration guidance, and fix the assumptions deliberately. Compose test suites are valuable because they catch UI behaviour regressions. They are less valuable if nobody understands why they pass.