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
You can install a package. So presumably, an .APK built on the Linux Travis container can be passed as a parameter to that, and it will be installed on the emulator (and presumably it would give back a "success!" or "failure!" message).
You can issue commands through shell, and among the commands you can run from a shell is to start an app:
It seems that if you combine this with the ability to push and pull files from the device, it would be possible to get back information on whether some kind of basic test finished successfully. Or it may not be necessary to do that, because all the work could be done by the shell on the phone...and then all you get is success or failure.
It's probably not necessary to automate a web browser to make sure the web console is working. Command line tests that wget or curl against localhost can probably test the server adequately (?)
In any case, the main idea would just be to have some kind of basic sense that it hadn't been broken...
Obviously designing this emulator-based-test is best tried out on a local Linux first! - I can try to help, but have a lot of things to do...including once this gets implemented, I'll be maintaining it whenever I break it, so maybe it's in your best interest to make sure this happens. :-)
The text was updated successfully, but these errors were encountered:
It is possible to run an android emulator on Travis, and there are commands in the "Android Debug Bridge" to interact with this emulator:
https://developer.android.com/studio/command-line/adb#issuingcommands
You can install a package. So presumably, an .APK built on the Linux Travis container can be passed as a parameter to that, and it will be installed on the emulator (and presumably it would give back a "success!" or "failure!" message).
You can issue commands through shell, and among the commands you can run from a shell is to start an app:
https://stackoverflow.com/a/4567928/211160
It seems that if you combine this with the ability to push and pull files from the device, it would be possible to get back information on whether some kind of basic test finished successfully. Or it may not be necessary to do that, because all the work could be done by the shell on the phone...and then all you get is success or failure.
It's probably not necessary to automate a web browser to make sure the web console is working. Command line tests that wget or curl against localhost can probably test the server adequately (?)
In any case, the main idea would just be to have some kind of basic sense that it hadn't been broken...
Obviously designing this emulator-based-test is best tried out on a local Linux first! - I can try to help, but have a lot of things to do...including once this gets implemented, I'll be maintaining it whenever I break it, so maybe it's in your best interest to make sure this happens. :-)
The text was updated successfully, but these errors were encountered: