Theming: Set the default theme to auto, and archive captured screenshots in github actions. #97
caarmenAnnotations
5 errors and 1 warning
|
IntegrationTest.themeTest:
app/src/androidTest/java/ca/rmen/android/poetassistant/main/IntegrationTest.java#L216
androidx.test.espresso.base.AssertionErrorHandler$AssertionFailedWithCauseError: '(an instance of android.view.View and an instance of android.widget.Checkable) and view.isChecked() matching: is <true>' doesn't match the selected view.
Expected: (an instance of android.view.View and an instance of android.widget.Checkable) and view.isChecked() matching: is <true>
|
|
ScreenshotTest.testTakeScreenshots[Light]:
app/src/androidTest/java/ca/rmen/android/poetassistant/main/ScreenshotTest.java#L1
java.lang.SecurityException: Error granting runtime permission
at android.app.UiAutomation.grantRuntimePermissionAsUser(UiAutomation.java:1433)
|
|
ScreenshotTest.testTakeScreenshots[Dark]:
app/src/androidTest/java/ca/rmen/android/poetassistant/main/ScreenshotTest.java#L1
java.lang.SecurityException: Error granting runtime permission
at android.app.UiAutomation.grantRuntimePermissionAsUser(UiAutomation.java:1433)
|
|
TaskStackTest.dictionaryDeepLinkAfterThemeChangeTest:
app/src/androidTest/java/ca/rmen/android/poetassistant/main/TaskStackTest.java#L73
java.lang.RuntimeException: Could not launch intent Intent { flg=0x10000000 cmp=ca.rmen.android.poetassistant.test/ca.rmen.android.poetassistant.settings.SettingsActivity } within 45000 milliseconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1736009706684 and now the last time the queue went idle was: 1736009711699. If these numbers are the same your activity might be hogging the event queue.
at androidx.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:537)
|
|
TaskStackTest.queryDeepLinkAfterThemeChangeTest:
app/src/androidTest/java/ca/rmen/android/poetassistant/main/TaskStackTest.java#L79
java.lang.RuntimeException: Could not launch intent Intent { flg=0x10000000 cmp=ca.rmen.android.poetassistant.test/ca.rmen.android.poetassistant.settings.SettingsActivity } within 45000 milliseconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1736009755487 and now the last time the queue went idle was: 1736009760517. If these numbers are the same your activity might be hogging the event queue.
at androidx.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:537)
|
|
Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
apks
|
30.6 MB |
|
|
coverage
|
632 KB |
|
|
instrumentation-tests
|
29.9 KB |
|
|
logcat
|
1.45 MB |
|
|
unit-tests
|
39.9 KB |
|