`DisplaySizeRule` does not consistently set back the previous emulator state
@paigemca is already working on this.
Since Jan 27, 2025.
Assessment
This issue has not been assessed yet.
Description
Actual
The emulator remains with the display size modified. Wiping the device is required to restore the original state.
Full test code (if helpful)
@OptIn(ExperimentalTestApi::class)
@RunWith(AndroidJUnit4::class)
class AppNavigationTests {
@get:Rule(order = 0)
val koinRule = KoinTestRule(
modules = listOf(
module {
singleOf(::FakeConferenceRepository) bind ConferenceRepository::class
viewModelOf(::MainViewModel)
}
)
)
@get:Rule(order = 1)
val composeRule = createAndroidComposeRule<ComponentActivity>()
@get:Rule(order = 2)
var displaySizeRule: DisplaySizeRule = DisplaySizeRule()
@Test
fun should_display_bottom_bar_when_compact() {
onDevice().setDisplaySize(
widthSizeClass = WidthSizeClass.COMPACT,
heightSizeClass = HeightSizeClass.MEDIUM
)
composeRule.setContent {
Red30TechApp()
}
composeRule
.onNodeWithTag("ui:bottomBar").assertIsDisplayed()
}
@Test
fun should_display_rail_when_medium() {
onDevice().setDisplaySize(
widthSizeClass = WidthSizeClass.MEDIUM,
heightSizeClass = HeightSizeClass.MEDIUM
)
composeRule.setContent {
Red30TechApp()
}
composeRule
.onNodeWithTag("ui:navigationRail").assertIsDisplayed()
}
}
Expected
The emulator is restored to its original state.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 342
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from android/android-test
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
android/android-test#681 · 2 comments · 1 reaction ·
-
ξεκσνδξδ Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2499 ·
-
ησξξσ Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2498 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
android/android-test#2473 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
android/android-test#2461 · 6 comments · 4 reactions ·
All issues in android/android-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100