Fix Intents init/release in UI tests #79
Labels
bug
Something isn't working
good first issue
Good for newcomers
refactoring
Moves or deletes files in the project
As of now, initialization and release of intents are done at the beginning and the end of each Android UI test. Therefore, sometimes when a tests fails it doesn't release its intents (as it is supposed to happen after the assertions), which non-deterministically crashes other tests that then look like they double initialize their intents.
Example of such code:
To fix this, one way could be to use the
@Before
and@After
annotations to initialize and release the intents, therefore avoiding code duplication and enforcing that the release is always done.The text was updated successfully, but these errors were encountered: