android / android/android-test
activityMatchesIntent prevent intent alteration
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 342
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 2
Description
To avoid handling intent twice, we nullify the data of the intent after having processed it during the activity `onCreate` phase. It works great but it makes our test fails because of `activityMatchesIntent` test during scenario launch. How should we deal with that?
https://github.com/android/android-test/blob/5c406a14c0393a393f624348ca05562523d78189/core/java/androidx/test/core/app/ActivityScenario.java#L465-L479
Contributor guide
Research direction
Start in core/java/androidx/test/core/app/ActivityScenario.java at lines 465-479 and inspect the activityMatchesIntent test during scenario launch. Determine how the test should handle intent data being nullified after onCreate processing; done means the intent is not handled twice and the scenario-launch test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile-dev, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100