microsoft / microsoft/AdaptiveCards
[Android] UI Test Stability improvements
Open
Nobody has claimed this yet.
Task
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
See android-ci.yml pipeline failures. Consider:
- Configuring test timeouts so that failures don't take an hour to show up
- Adding retry logic if it's deemed helpful
- Containerizing the whole thing if it would be helpful
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the android-ci.yml pipeline and review the failures it references, focusing on where UI tests wait or time out. Determine which stability measure is in scope—timeouts, retries, or containerization—and validate the result by running the Android UI test workflow with failures completing sooner and more reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- ci-cd, mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100