Releases: sergio-sastre/AndroidUiTestingUtils
2.6.0
✅ Paparazzi 1.3.4 -> 1.3.5
✅ Roborazzi 1.26.0 -> 1.32.2
✅ Robolectric 4.13 -> 4.14
Paparazzi & Roborazzi
- overrideForDefaultAccessibility() to easy enable Accessibility
- support custom Density when defining Device
Paparazzi:
- Support 2.3.5
- Support useDeviceResolution & validateAccessibility
Roborazzi:
- Support 1.32.2
- Support record WebP & aiAssertions
2.5.0
Library compatibility updates
✅ Paparazzi 1.3.3 -> 1.3.4
Info
Paparazzi 1.3.4 made some API changes in Density, what resulted in crashes if using it for Cross-Library screenshot tests with AndroidUiTestingUtils. This version makes possible Cross-Library screenshot tests with Paparazzi 1.3.4
2.4.0
Library compatibility updates
✅ Android-Testify 2.1.0 -> 3.2.0
✅ Roborazzi 2.12.0 -> 2.26.0
✅ Robolectric 4.12.1 -> 4.13
What's new!
Android-Testify
🆕 New extension methods to simplify its integration with ActivityScenarios
🆕 New CrossLibrary options (e.g. useSoftwareRendering)
Roborazzi
🆕 New CrossLibrary options: RecordOptions (i.e. applyDeviceCrop & resizeScale),
2.3.5
- Downgrade some dependencies in
:utils
that only throw exceptions when running Android-Testify with GradleManagedDevices
2.3.4
2.3.3
2.3.2
Library upgrades
- Roborazzi to 1.12.0
2.3.1
Library upgrades
- Roborazzi to 1.11.0
- Robolectric to 4.12.1
NOTE
Robolectric 4.12.1 Supports Native Graphics on Windows. Therefore, you could run Roborazzi screenshot tests on Windows as well (theoretically)!
2.3.0
FontSize Config (no breaking changes)
- Custom Values e.g.
FontSizeScale.Value(1.25f)
- Default Non-Linear values e.g.
FontSize.XXXLARGE //1.8f
Cross-Library updates
- Shot 6.1.0 + maxPixels
- Roborazzi 1.10.1 + ImageComparator & Metadata
- Paparazzi 1.3.3
2.2.1
Release with bug fixes only!
- Fix DisplaySize and FontSize not resetting values when the test fails or throws an exception in Instrumentation Activity Screenshot Tests #105
- Call waitForSync() to AndroidTestifyScreenshotTestRuleForView (used in Cross-Library screenshot tests with Android-Testify) before asserting screenshot to avoid flakiness