-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Testing] Added new SafeAreaEdges categories in UITest and created separate lane to run the category in API 36 [2] #31631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: net10.0
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enhances the UI test pipeline by adding support for Android API level 36 and creating targeted testing for SafeAreaEdges functionality. The changes enable more comprehensive test coverage and precise control over test environments for specific features.
- Added Android API 36 to the supported API levels for broader test coverage
- Created a dedicated pipeline stage for SafeAreaEdges tests on Android API 36 with Pixel 7 device configuration
- Added deviceType parameter support to enable specification of Android device skins in test runs
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/pipelines/common/ui-tests.yml | Added API 36 support, SafeAreaEdges test filter, and dedicated SafeAreaEdges test stage |
| eng/pipelines/common/ui-tests-steps.yml | Added deviceType parameter and ANDROID_TEST_SKIN environment variable support |
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| path: ${{ project.android }} | ||
| app: ${{ project.app }} | ||
| device: android-emulator-64_36 | ||
| deviceType: "pixel_7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creating AVD: Emulator_36 (system-images;android-36;google_apis_playstore;x86_64)...
Resolved tool to path /usr/local/lib/android/sdk/cmdline-tools/latest/bin/avdmanager
Executing: /usr/local/lib/android/sdk/cmdline-tools/latest/bin/avdmanager create avd -n Emulator_36 -k "system-images;android-36;google_apis_playstore;x86_64" --device "pixel_7" --force
Error: No device found matching --device pixel_7.
null
Starting Emulator: Emulator_36...
adb: no devices/emulators found
|
/rebase |
41d9c5d to
2c068f4
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/rebase |
2c068f4 to
fd3b76a
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
This pull request updates the UI test pipeline configuration to support targeted testing of the
SafeAreaEdgesfeature on Android API level 36, and adds flexibility for specifying device types in test runs. The changes improve test coverage and allow for more precise control over test environments.Android test coverage and configuration improvements:
androidApiLevelsparameter to include both 30 and 36.android_ui_tests_safeareas_api36) to runSafeAreaEdgestests specifically on Android API 36 using the Pixel 7 device skin.Test filtering and device configuration enhancements:
SafeAreaEdgesto the list of test filters, enabling targeted execution of these tests.deviceTypeparameter toui-tests-steps.yml, allowing specification of the Android device skin/type for test runs.ANDROID_TEST_SKINvariable whendeviceTypeis provided, ensuring the correct device skin is used during test execution.Note: This PR contains only the YAML pipeline updates and is a continuation of #31355
Fixes #32059