\n One important note is that the Compose library is based on the view system library, so you only need to import one version<\/strong> in any project. If you\u2019re only using views, then you should import the view system library:<\/p>\n Otherwise, you should import the Compose library:<\/p>\n \n The view system library<\/a> is the basis of the Test Kit and was originally created because we found ourselves using the same helper functions over and over again in our UI tests. When you import the library, you\u2019ll have access to the following utilities:\n<\/p>\n \n Set up and support a test scenario from an \n Simulate dual-screen swipe gestures on both Surface Duo models and change device orientation.\n<\/p>\n<\/li>\n \n Simulate folding features with different properties, including those of other foldable devices, with the Jetpack Window Manager testing artifact<\/a>.\n<\/p>\n<\/li>\n \n Simulate a force click with a \n Check if a view is shown in the display area given its position and screen dimensions.\n<\/p>\n<\/li>\n \n Monitor and reset \n The Compose library<\/a> builds on the view system library by adding helper functions that are useful for Compose UI tests. When you import this library, you\u2019ll have access to all of the functionality described above, in addition to the following Compose utilities:\n<\/p>\n \n Provides Compose wrappers for the \n Access string resources during UI tests with an \n If you\u2019ve been following our blog in the past, you may have seen our posts about foldable testing tips with Espresso<\/a> and Jetpack Compose<\/a>. \n<\/p>\n Code snippet from Surface Duo testing tips & tricks blog post for spanning during an Espresso test<\/em>\n<\/p>\n \n You may have also tried out foldable testing in the Jetpack Window Manager codelab<\/a>. \n<\/p>\n Code snippet from JWM codelab for simulating a folding feature<\/em>\n<\/p>\n \n Either way, you can see how these code snippets could be hard to understand from a beginner\u2019s point-of-view and could lead to mistakes due to incorrect swipe coordinates or folding feature properties. With the Test Kit, our goal was to make tests more readable and easier to write. In the modified code snippets below, you can see how the same tests would look when using our libraries:\n<\/p>\n Updated code snippet based on Surface Duo testing tips & tricks blog post that uses the Test Kit to span during an Espresso test<\/em>\n<\/p>\n Updated code snippet based on JWM codelab that uses the Test Kit to simulate a folding feature<\/em>\n<\/p>\n \n You can see how you no longer need to calculate the exact coordinates for a swipe; in the library, we dynamically determine the coordinates by checking the size and orientation of a device. And for simulating folding features, it\u2019s a lot easier to focus on passing in the relevant properties now that the boilerplate code is part of the helper method implementation.\n<\/p>\n \n When writing your own foldable tests, we hope you also find that the Test Kit makes the whole process easier!\n<\/p>\n \n To import the Test Kit, follow these steps:\n<\/p>\n View system library<\/strong>\n<\/p>\n Compose library<\/strong><\/p>\n \n Once you\u2019ve imported the correct library version, you can start setting up your test classes and writing tests. To test UI behavior on foldables, you have two options: swipe gestures<\/a> or mock folding features<\/a>.\n<\/p>\n \n The first option works best on dual-screen devices like Surface Duo, where certain gestures are needed to change app display state. Our helper methods use the \n Figure 1. Animation of the \n The second option works on all kinds of foldables, so we would recommend using this approach to make sure your apps work well on many devices. Our helper methods use the Jetpack Window Manager testing artifact<\/a> to send mock folding features to a test rule\u2019s activity. The animation below shows a UI test from our Compose NavigationRail sample<\/a> that simulates a vertical folding feature:\n<\/p>\n \n Figure 2. Animation of the \n To see more examples of how to use the Test Kit, check out these resources:\n<\/p>\ncom.microsoft.dualscreen.testing:testing-kotlin<\/pre>\n
com.microsoft.dualscreen.testing:testing-compose<\/pre>\n
View system library<\/h3>\n
\n
ActivityTestRule<\/code> and helps you to ensure that the Activity is running before to use any view or assertion, and any configuration change.\n<\/p>\n<\/li>\nViewAction<\/code> extension used specifically after configuration changes.\n<\/p>\n<\/li>\nWindowLayoutInfo<\/code> data in a test activity.\n<\/p>\n<\/li>\n<\/ol>\nCompose library<\/h3>\n
\n
FoldingFeatureHelper<\/code> methods from the view system library.\n<\/p>\n<\/li>\nAndroidComposeTestRule<\/code>.\n<\/p>\n<\/li>\n<\/ol>\nWrite foldable tests with less code<\/h2>\n
@Test \r\nfun\u202fisAppSpanned()\u202f{\r\n \u202f\u202f\u202fval\u202fdevice\u202f=\u202fUiDevice.getInstance(InstrumentationRegistry.getInstrumentation()) \r\n\r\n\u202f\u202f\u202f\u202f\/\/ span the app (from the left side) \r\n\u202f\u202f\u202f\u202fdevice.swipe(675,\u202f1780,\u202f1350,\u202f900, 400)\u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f\r\n\r\n \u202f\u202f\u202f\/\/ test a UI element \r\n\u202f\u202f\u202f\u202fonView(withText(\"your-text-to-test\")).check(matches(isDisplayed())) \r\n}<\/pre>\n@Test\r\nfun testText_is_left_of_Vertical_FoldingFeature() {\r\n\u00a0 \u00a0activityRule.scenario.onActivity { activity ->\r\n\u00a0 \u00a0 \u00a0 \u00a0val hinge = FoldingFeature(\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0activity = activity,\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0state = FLAT,\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0orientation = VERTICAL,\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0size = 2\r\n\u00a0 \u00a0 \u00a0 \u00a0)\r\n\u00a0 \u00a0 \u00a0 \u00a0val expected = TestWindowLayoutInfo(listOf(hinge))\r\n\u00a0 \u00a0 \u00a0 \u00a0publisherRule.overrideWindowLayoutInfo(expected)\r\n\u00a0 \u00a0}\r\n\r\n\u00a0 \u00a0\/\/ Add Assertion with EspressoMatcher here\r\n}<\/pre>\n@Test \r\nfun\u202fisAppSpanned()\u202f{\r\n \u202f\u202f\u202fval\u202fdevice\u202f=\u202fUiDevice.getInstance(InstrumentationRegistry.getInstrumentation())\r\n \t\r\n\u202f\u202f\u202f\u202f\/\/ span the app (from the left side) \r\n device.spanFromStart()\r\n\r\n\u202f\u202f\u202f\u202f\/\/ test a UI element \r\n\u202f\u202f\u202f\u202fonView(withText(\"your-text-to-test\")).check(matches(isDisplayed())) \r\n}<\/pre>\n@Test\r\nfun testText_is_left_of_Vertical_FoldingFeature() {\r\n publisherRule.simulateVerticalFoldingFeature(activityRule, size = 2, state = FLAT)\r\n\r\n\u00a0 \u00a0\/\/ Add Assertion with EspressoMatcher here\r\n}<\/pre>\nAdd to your project<\/h2>\n
\n
mavenCentral()<\/code> repository in your top-level build.gradle<\/strong> file:<\/p>\nallprojects {\r\n repositories {\r\n google()\r\n mavenCentral()\r\n }\r\n}<\/pre>\n<\/li>\ncompileSdkVersion<\/code> and targetSdkVersion<\/code> are set to API 31 or newer in your module-level build.gradle<\/strong> file:<\/p>\nandroid { \r\n compileSdkVersion 31\r\n defaultConfig { \r\n targetSdkVersion 31 \r\n } \r\n ...\r\n}<\/pre>\n<\/li>\nimplementation \"com.microsoft.dualscreen.testing:testing-kotlin:1.0.0-alpha2\"<\/pre>\n
implementation \"com.microsoft.dualscreen.testing:testing-compose:1.0.0-alpha03\"<\/pre>\n<\/li>\n<\/ol>\n
swipe<\/code> method from the UiAutomator<\/a> testing framework to simulate gestures like spanning, unspanning, switching, and closing apps. The animation below shows a UI test from our dual-screen experience example<\/a> that performs a spanning swipe:\n<\/p>\n![\"Animation](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2022\/03\/animation-of-the-openproductsinduallandscapemode.gif\")
\n<\/p>\nopenProductsInDualLandscapeMode<\/code> test<\/em>\n<\/p>\n![\"Animation](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2022\/03\/animation-of-the-app_verticalfold_testplaceholder.gif\")
\n<\/p>\napp_verticalFold_testPlaceholderViewAppearsOnStart<\/code> test<\/em>\n<\/p>\nSamples<\/h2>\n