commit | f61c557f4526dfa0e33d070de9c262e788184e8a | [log] [tgz] |
---|---|---|
author | Zach Klippenstein <klippenstein@google.com> | Thu Oct 20 10:33:11 2022 -0700 |
committer | Zach Klippenstein <klippenstein@google.com> | Wed Nov 30 10:12:08 2022 -0800 |
tree | 294c8543feb1f561d33123ddae82dc172d76a2e0 | |
parent | d182d8af38f407dcb35599126c6c7534381abe25 [diff] |
Defer dispatching coroutines resumed during animation callbacks in UI tests. This is a workaround for the fact that we use an unconfined dispatcher in UI tests (b/254115946), which prevents us from being able to perform layout passes for frames in some cases (b/222093277). TestMonotonicFrameClock gets a continuation interceptor which wraps continuations with behavior that will usually no-op, but if the continuation is resumed while frame callbacks are running, it will defer resuming the underlying continuation until all the frame callbacks have finished. This matches how continuations are dispatched in non-test code, since that code does not use an unconfined dispatcher. In order to preserve test delay skipping, the interceptor implements Delay and delegates it to the underlying dispatcher, just like ApplyingContinuationInterceptor is already doing. This CL also adds a callback that runs after each frame in TestMonotonicFrameClock. This change was originally in aosp/2121435. This allows us to perform measure and layout after each frame if necessary, which aligns the measure/layout timing with production. Bug: b/254115946 Bug: b/222093277 Bug: b/255802670 Test: PhaseOrderingTest, TestMonotonicFrameClockTest Relnote: "In UI tests using a Compose rule, continuations resumed during `withFrameNanos` callbacks will not be dispatched until after all frame callbacks have finished running. This matches the behavior of compose when running normally. However, tests that rely on the old behavior may fail. This should only affect code that calls `withFrameNanos` or `withFrameMillis` directly, and has logic outside of callback passed to those functions that may need to be moved inside the callbacks. See the animation test changes in this CL for examples." Relnote: "Added optional `onPerformTraversals: (Long) -> Unit` parameter to `TestMonotonicFrameClock` constructor and factory function to run code after `withFrameNanos` callbacks but before resuming callers' coroutines." Change-Id: Idb41309445a030c91e8e4ae05daa9642b450505c
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.