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
{{ message }}
Repository navigation
Create an app for testing p4a builds on the device #1630
The app should import each of its included modules and do a basic test of them before exiting. This can be automated with unittest. This on-device test can then be used to test the state of python-for-android beyond only checking that the builds complete. It can also possibly be automated in the future.
Discussed with @AndreMiras, will probably aim for an initial proof of concept very soon.
@hackalog@AndreMiras has been looking at automation, not sure about the state of it. However, just having an app that can be run and assessed from the logcat output alone is already a nice improvement, even if it has to be started manually.
Activity
inclement commentedon Jan 30, 2019
Closing via #1636. The app needs lots of features to fulfil the detailed goals we might have, but the basic core is there for now.
hackalog commentedon Jan 31, 2019
I was thinking of doing something similar in ios. How are you planning on testing (automating) that the app ran on the device correctly?
inclement commentedon Jan 31, 2019
@hackalog @AndreMiras has been looking at automation, not sure about the state of it. However, just having an app that can be run and assessed from the logcat output alone is already a nice improvement, even if it has to be started manually.
AndreMiras commentedon Feb 1, 2019
@hackalog yes confirmed we're working on automated runtime checking on Android #1637
For iOS you should take a look at https://github.com/kivy/kivy-ios