talk,
such as native support for .
We are also happy to announce that, starting with version 1.0, we're
distributing releases on Google's Maven repository, which makes it a lot easier
to use ATSL in your builds. To learn more about using this repository, see the
to , the platform includes support for instrumenting tests outside of your
app's default process. (Prior to Android O, you could only test against app
components in your app's default process.) Multiprocess Espresso makes this
support possible. It allows you to seamlessly test your app's UI interactions
that cross process boundaries while still maintaining Espresso's synchronization
guarantees.
The good news is that Espresso does all the work; you don't have to change
anything for setups with UI in multiple processes. You can keep writing your
Espresso tests like you would for single process apps, and Espresso
automatically handles the process IPC and synchronization between processes.
The following diagram shows how multiple instances of Espresso communicate with
each other:
and our API.
IdlingRegistry is a lightweight registry that doesn't bring in theentire Espresso library, so you can more easily register resources from your
application code. When combining this API with Multiprocess Espresso, you can
register idling resources from any process within your application code.
Registration from the Espresso class is now deprecated.
Idling Resources
Writing custom idling resources can be time consuming, so Espresso 3.0.0 now
comes with more idling resources out of the box to synchronize your threads. The
new resources include: . There will be more to come!
To take advantage of the new idling resource, add these new dependencies to your
build.gradle file:
androidTestCompile "com.android.support.test.espresso.idling:idling-concurrent:3.0.0"
Additionally,
package that's located in Espresso idling resource. For the full migration
details, refer to our
objects, you can now use ProviderTestRule
instead of
documentation.
Grant Permission
Rule
Android M (API level 23) allows apps to request permissions at runtime. However,
the dialogs that request runtime permissions place tests in a state where they
cannot continue, causing them to fail. By using
Be aware that if your tests require shared state to pass, the
orchestrator causes them to fail. This behavior is by design. As of this post,
Android Test Orchestrator is in beta and is available for use via the command
line. We have integrations planned for Firebase Test Lab and Android Studio,
coming soon.
For more information, see the .
runner arguments
Sometimes you want to test an activity that you create and configure on the fly
as part of your test workflow. Now, you can configure )
using an .
Last but not least, we want to thank all the developers who contributed features
to this release. We also want to thank the Android testing experts on the mobile
engineering teams at American Express, Slack and GDE Chiu-Ki Chan for
collaborating with us and providing valuable feedback on the pre-release version
of Android Testing Support Library.
Happy testing from the ATSL team!
Community-Analysen & Experten-Meinungen 0
Verwandte Story-Cluster & Quellen (Vektor-KI)
SOCIAL SHARE CARD GENERATOR