Skip to main content

force android tests to run on different emulators from command line batch file



How can I run my android junit/robotium tests from the command line on every single emulator? I want to make sure my tests run on many android OS versions and many screen resolutions.





I'd like to write a batch file that runs from the windows command line to run my test suite over and over again on each emulator I have installed.





To run from the command line I can do this:







adb shell am instrument -w com.myapp.client.test/android.test.InstrumentationTestRunner







but that just runs it on the default emulator. How can I force that command to run on all of the emulators I have setup?





Ideally, the batch file would looking something like:





  1. launch emulator1



  2. run tests



  3. close emulator1



  4. launch emulator2



  5. run tests



  6. close emulator2



  7. ...







I don't know how to do the launch and close part.





Thanks








EDIT: Found solutions. Below is my batch file







set PORTRAIT=medium

set LANDSCAPE=large



:: launch emulator

emulator -avd android2.2



:: wait for emulator to load

adb wait-for-device



:: install apps?



:: run tests in portrait

adb shell am instrument -w -e size %PORTRAIT% com.myapp.client.test/android.test.InstrumentationTestRunner



:: run tests in landscape

adb shell am instrument -w -e size %LANDSCAPE% com.myapp.client.test/android.test.InstrumentationTestRunner



:: pull screenshots

adb pull /sdcard/ c:\



:: close/kill emulator (android bug here, so must use windows taskkill)

taskkill /IM emulator-arm.exe




Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex