Skip to content

Conversation

@NafeelaNazhir
Copy link
Contributor

@NafeelaNazhir NafeelaNazhir commented Sep 16, 2025

This pull request updates the UI test pipeline configuration to support targeted testing of the SafeAreaEdges feature 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:

  • Added support for running UI tests on Android API level 36 by updating the androidApiLevels parameter to include both 30 and 36.
  • Introduced a dedicated pipeline stage (android_ui_tests_safeareas_api36) to run SafeAreaEdges tests specifically on Android API 36 using the Pixel 7 device skin.

Test filtering and device configuration enhancements:

  • Added SafeAreaEdges to the list of test filters, enabling targeted execution of these tests.
  • Added a new deviceType parameter to ui-tests-steps.yml, allowing specification of the Android device skin/type for test runs.
  • Updated environment configuration to set the ANDROID_TEST_SKIN variable when deviceType is 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

@dotnet-policy-service dotnet-policy-service bot added community ✨ Community Contribution partner/syncfusion Issues / PR's with Syncfusion collaboration labels Sep 16, 2025
@NafeelaNazhir NafeelaNazhir added the area-testing Unit tests, device tests label Sep 16, 2025
@NafeelaNazhir NafeelaNazhir marked this pull request as ready for review September 16, 2025 13:34
@NafeelaNazhir NafeelaNazhir requested a review from a team as a code owner September 16, 2025 13:34
Copilot AI review requested due to automatic review settings September 16, 2025 13:34
Copy link
Contributor

Copilot AI left a 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

@PureWeen
Copy link
Member

/azp run MAUI-UITests-public

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jsuarezruiz
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

path: ${{ project.android }}
app: ${{ project.app }}
device: android-emulator-64_36
deviceType: "pixel_7"
Copy link
Contributor

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

@PureWeen
Copy link
Member

/rebase

@PureWeen
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@jsuarezruiz
Copy link
Contributor

/rebase

@jsuarezruiz
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-testing Unit tests, device tests community ✨ Community Contribution partner/syncfusion Issues / PR's with Syncfusion collaboration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants