Hi Zygmunt,
Hey everyone.
I'm trying to figure out a way to get connectivity manager tests enabled and pushed to LAVA. I read the code briefly (please correct any misconceptions I may have) and I see a few steps that need to be taken to achieve that.
1) We need to build them into our images. That's the obvious bit. It may be done already, I'm still digging through the code and the build system.
2) We need to script them so that they can execute given the correct environment. This part feels rather simple as there are explicit ADB commands in the comments throughout that code. I will try to build a comprehensive list of tests with notes and update you as I go. Still is should be relatively easy to script the execution
3) We need to work with the LAVA team to prepare a proper environment. So far this seems to be the biggest technical challenge. From my shallow understanding of the code we'd have to setup a few wireless access points with various configurations (or alternate the configuration on a single access point but that seems harder and more error prone) and see if we can get repeatable outcome from those connection tests.
The thing that worries me is the susceptibility to background noise / other transmissions / etc. It seems that most "interesting" tests are related to wireless communication. I wonder what is your opinion on this. Should we just enable all the tests that we technically can and ignore the fact that our test environment is not isolated?
Thanks for the feedback
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
_______________________________________________
linaro-android mailing list
linaro-android@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-android