search

posix4e / puppet

MIT License
8 stars 8 forks source link

Staging and Production Android instances running in the cloud #23

Open posix4e opened 1 year ago

posix4e commented 1 year ago

Rather than just relying on the developer emulator at build and test time, let's deploy android into the cloud so we can do continuous testing with a fixed UID. Probably with sauce labs.

This should be a real integration test not mocked, unit or end to end

leepopcan commented 1 year ago

Refer to "point the testing puppet to a specific UID / backend in a programatic way to use different backends"

Add a fixed UID / BASE_URL param in android manifest buildType[ debug ] node so the testing puppet will call to different backends programatic. It's easy. Did I understand correctly?

banjaminlee commented 1 year ago

Hi, I can start work immediately. Please check my cover letter on Upwork.

vkolgi commented 1 year ago

Added #27 to address this issue.

vkolgi commented 1 year ago

For UID and BASE_URL I would consider using buildConfigFields per buildType. So for release and debug buildConfigField will read the UID and BASE_URL from environment variable. That way the UID isn't checked into the source code if thats a concern, however can be injected by CI.