activityMatchesIntent prevent intent alteration

Open
#1,939 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
mobile-dev, testing

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.

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

Dominant language
Java
Stars
1.2k
Forks
342
Avg merge
1d 14h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from android/android-test

All issues in android/android-test

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.