dotnet / dotnet/runtime

[android][infra] Validate .NET 11 Android functionality across different API versions

Open
#122,021 2 comments 0 reactions 1 assignee Claimed by @simonrozsival View on GitHub
area-Infrastructure-mono os-android test-enhancement
Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

## Why
Android versions come with broad range of different API versions. Currently, most of our testing uses only API 29 (e.g. Android emulators `Ubuntu.2204.Amd64.Android.29.Open`). However, in .NET 11, we support API levels 21(?) and higher. We should periodically test functionality on different API versions.

## How
Description of how the testing is done, can be found in https://github.com/dotnet/runtime/issues/107868. Previous test run e.g., https://github.com/dotnet/runtime/pull/120093. In addition, to testing Mono Android scenarios, we should also include CoreCLR in this testing.

## What
This verification makes the most sense to be done on the pre-release branch of dotnet/runtime. Optionally, we can also verify servicing branches if we await any issues. Throughout the release cycle, this validation should be performed periodically to prevent unexpected issues caused by un-tested API levels.

This verification should be performed periodically throughout the Preview and RC release cycle, an example of verification schedule:
- [x] Preview 1
- [x] Preview 4
- [x] Preview 5
- [x] Preview 7
- [ ] RC2

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.