Improve Emulator Lifecycle Reliability and Tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, csharp
- Domain
- mobile-dev, testing-qa
Research direction
Start with the WaitForBootComplete and WaitForCpuLoadBelow entry points, then compare their exception handling with GetEmulatorName and the fix described in PR #56. Add unit or integration coverage for transient adb failures and timeout behavior; done means both wait methods retry gracefully without failing immediately.
Written by the indexing model from the issue text.
Description
As discussed in PR #63 review, the new emulator lifecycle methods (WaitForBootComplete, WaitForCpuLoadBelow) need hardening.
Tasks:
- Add try-catch handling for SdkToolFailedExitException in WaitForBootComplete (similar to GetEmulatorName fix in PR #56)
- Add try-catch handling for SdkToolFailedExitException in WaitForCpuLoadBelow
- Add unit/integration tests for these wait methods to ensure they handle transient adb failures gracefully
- Verify timeout behaviors
Context:
adb commands can fail transiently during emulator boot. The current implementation might throw exceptions immediately instead of retrying, potentially causing flaky tests or CI failures.
- Dominant language
- C#
- Stars
- 78
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from Redth/AndroidSdk.Tools
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
Redth/AndroidSdk.Tools#85 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Redth/AndroidSdk.Tools#84 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Redth/AndroidSdk.Tools#65 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Redth/AndroidSdk.Tools#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Redth/AndroidSdk.Tools#41 ·
All issues in Redth/AndroidSdk.Tools
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fluentassertions/fluentassertions#3353 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
unoplatform/uno#24769 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22323 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/onnxruntime-genai#2633 ·
Maintainers usually reply within 1 day