You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not recommended to hardcode the host ports that docker maps a container's ports to in order to avoid clashes with ports already in use. This shouldn't really matter on Github's CI due to the isolation, but it's still good practice.
This will require passing the ports into the test apk running on the emulator/device, which in turns needs a custom test runner (a subclass of AndroidJUnitRunner ). If started viaadb shell am instrument, args can be passed and read by the subclass and used in the tests.
This is all quite involved and the integration tests are fine right now, so this is low priority, just for documentation's sake.
The text was updated successfully, but these errors were encountered:
It's not recommended to hardcode the host ports that docker maps a container's ports to in order to avoid clashes with ports already in use. This shouldn't really matter on Github's CI due to the isolation, but it's still good practice.
This will require passing the ports into the test apk running on the emulator/device, which in turns needs a custom test runner (a subclass of AndroidJUnitRunner ). If started via
adb shell am instrument
, args can be passed and read by the subclass and used in the tests.This is all quite involved and the integration tests are fine right now, so this is low priority, just for documentation's sake.
The text was updated successfully, but these errors were encountered: