commit | 2b161e41d15a571b901db554f5c178b9e052caef | [log] [tgz] |
---|---|---|
author | Filip Pavlis <pavlis@google.com> | Fri Nov 22 17:40:08 2019 +0000 |
committer | Filip Pavlis <pavlis@google.com> | Tue Dec 10 15:29:32 2019 +0000 |
tree | 834360b9c5134f07f7dfa801a4f7fae98bb4a07e | |
parent | 65b50b31a1e7daf3cc742fbf56ca9bbcb5793a9e [diff] |
Improvements in Compose testing lib sync. After trying to setup tests for jetnews I identified several issues in our synchonization. After fixing these several other issues surfaced that were previously hidden by incorrect sync. I have introduce ComposeIdlingResource that registers itself into Espresso. This way we leave synchronization to Espresso. It removed several flakes we had because we used to wait for idle compose and then did the "Espresso wait". From now on Espresso does all of it at the same time. This helps in cases where we have regular Android event that later leads to invalidation of compose. Thanks to us having ComposeIdlingResource we no longer need to wait after we perform actions (doClick) for idle Compose. It also makes tests faster as we don't sync when not needed. This unfortunately broke tests that were relying on this fact (incorrectly) and touching the UI thread from the test thread. So far lots of tests were using waitForIdleCompose() and touching variables from different threads or did not use any kind of synchonization at all. They were lucky because methods like doClick used to wait for UI being idle before leaving. To address that I have introduced runOnIdleCompose that waits for idle compose and performs the given lambda on the UI thread. This makes assertions nice and stable! :) I have also removed waitForIdle {} as it would encourage bad practices from now on. Other thing discovered after I removed the flakes was that we were always recreating SemanticsConfiguration which previsouly wasn't detected. This however was something on which the testing API relied on. So I memoized the SemanticsConfiguration. This will need to work with merging also. We were also not disposing compositions between tests. This lead to more synchronization issues as old compositions were still part of the app. Another wrong thing was that we always send any events to the first ComposeView. This was wrong in case the second ComposeView would need to work with events. It wasn't detected becase MultipleComposeRootsTest had wrong assertions. Now it is fixed. Unfortunately I had to fix several tests so sorry for the diff. However I couldn't split it because the sync changes go hand in hand with how the tests are written. Bug: b/122349846 Test: Verified on current tests and local JetNews tests. Change-Id: If58d3c300e430de4ce81a7e4a963e41c04f71b5b
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.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "you@example.com"
mkdir androidx-master-dev cd androidx-master-dev
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ./studiow
and accept the license agreement when prompted. Now you're ready edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put the following at the top of your ‘repositories’ property in your project build.gradle
file:
maven { url '/path/to/checkout/out/androidx/build/support_repo/' }
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.
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-4v-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
cd path/to/checkout/frameworks/support/ repo start my_branch_name . # make needed modifications... git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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.