Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ff533ba4 authored by Riddle Hsu's avatar Riddle Hsu
Browse files

Use simple home key for setup 

The step in setup is not the major action to verify. And because
tapl may use its context configuration rotation to assert (may
not be updated in time), that causes some unnecessary failures.

The test is to verify the animation when launching from notification,
so how to return to home in setup is not so important.

Bug: 244414110
Test: atest FlickerTestsOpen:AppFromLockNotificationWarm
Change-Id: I94382fdab3beb92d3740bd1850ee2ae7f4d8d0c9
parent 05562ecd

tests/FlickerTests/src/com/android/server/wm/flicker/launch/OpenAppFromNotificationWarm.kt

+1 −9
Original line number Diff line number Diff line
@@ -19,7 +19,6 @@ package com.android.server.wm.flicker.launch 
import android.platform.test.annotations.FlakyTest

import android.platform.test.annotations.Postsubmit

import android.platform.test.annotations.RequiresDevice

import android.view.Surface

import android.view.WindowInsets

import android.view.WindowManager

import androidx.test.uiautomator.By
@@ -75,14 +74,7 @@ open class OpenAppFromNotificationWarm( 
                    .withFullScreenApp(testApp)

                    .waitForAndVerify()

                testApp.postNotification(wmHelper)



                if (testSpec.isTablet) {

                    tapl.setExpectedRotation(testSpec.startRotation)

                } else {

                    tapl.setExpectedRotation(Surface.ROTATION_0)

                }



                tapl.goHome()

                device.pressHome()

                wmHelper.StateSyncBuilder()

                    .withHomeActivityVisible()

                    .waitForAndVerify()