On Tue, 19 Feb 2019 at 05:24, ankit gupta ankitrtk@gmail.com wrote:

Hi All,

I am new to Android testing, I am using standard board i.mx6/rpi3 and flashed Android on it, I can connect with these board using "adb" tool.

I want to do some system test using LAVA framework, and I don't want to reflash image every time(wants to test on the existing system). Can someone please let me know how I can do Android testing on existing flashed image?

This is not recommended - see the documentation on the problems of simplistic testing and persistence.

https://master.lavasoftware.org/static/docs/v2/simple-admin.html#problems-wi...

The other side to this is that if you really never need to reflash the base system, you probably don't need to be testing on real hardware at all. Testing in emulation will actually be more efficient. The exception to this are performance benchmarks but there are costs here too - admins need to interact with the always-on devices. Some devices fail to charge the battery when left in bootloader modes, etc.

Please reconsider how you are planning on testing - it doesn't sound like you need to be testing on real hardware in the first place. Think carefully about your Test Plan. If all you are doing is experimenting, that can be done using adb alone. If you are planning an actual CI loop linked to a development cycle, you will need to review that plan and choose between flashing the images onto real hardware or using emulation. "Connect & test" methods are not suitable for a useful CI system. Just because you have a board available doesn't mean that emulation would not be a better choice. Emulation can allow testing on multiple emulated boards, real hardware in LAVA restricts you to only the boards you can integrate into LAVA.

A simplistic approach to testing will not save you time in the long run. Yes, flashing images may take a long time but this does not mean that this can be avoided. It is a problem inherent in Android testing because of the Android system design.

Also, the imx6 is not currently supported for Android testing in LAVA, only U-Boot testing. You would need to integrate the device into LAVA as a new Android device-type which is not necessarily easy.

https://master.lavasoftware.org/static/docs/v2/device-integration.html#addin...