| commit | 67abefb089736bbd34425562961df0a47f846244 | [log] [tgz] |
|---|---|---|
| author | Shamali P <[email protected]> | Mon Aug 07 19:27:40 2023 +0000 |
| committer | Shamali P <[email protected]> | Wed Aug 23 21:32:47 2023 +0000 |
| tree | 52f8076c101a8b553e9c01e305811f4aed9c5896 | |
| parent | 34ede8799a022385ca94a1bc111f978ac2e65f45 [diff] |
[Unit test lib] Add `runGlanceAppWidgetUnitTest` similar to compose's `runComposeUiTest` that provides scoped functions such as `provideContent`, `onNode` etc. to be able to write unit tests.
* `onAllNodes` and corresponding assertions on collections will be in follow up.
* Similarly more filters coming up in follow up.
* In general I'd imagine most Glance usages to load data in `provideGlance`, but since technically it is possible to use a LaunchedEffect, so, uses `runTest` (StandardTestDispatcher) and added a awaitIdle function if they would like to wait for delays etc. from their launched effects.
* In compose it also supports passing effectContext for launchedEffects, but that's mostly for usage with animations which we don't have. So didn't include it, but would rather let us see how it goes without it.
Bug: b/201779038
Test: Ran 60 iterations of "i=0; while echo "iteration $i" && ./gradlew :glance:glance-appwidget-testing:testDebugUnitTest ; do i=$((i+1)); done"
Relnote: """Adds `runGlanceAppWidgetUnitTest` that provides scope to
call methods on `GlanceAppWidgetUnitTest` such as
`provideComposable` to provide a small isolated composable for test,
`onNode` to find a Glance composable element in the provided
content. This enables you to write unit tests for individual
composable functions in your appWidget to verify that given
certain inputs the function outputs the intended set of glance
composable elements.
"""
Change-Id: I2f682d9ee00def5d768bd41f44cc097fc049794b
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(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.
