Bai---Fall swallow fly first heavy Android unit test instrumentation and Irobotium

PS: Called the white---falling yan pure fun (the end of the Moon game screen sense, the impact, collision despite the unsatisfactory, but the white this profession is good, used as the beginning, to do a narration just).

The unit test here whether it is instrumentation or irobotium are not suitable for the game, the game's own initiative to participate in the company Wetest based on the engine of the object identification of their own proactive solution or in front of the Sikuli scheme. This applies only to the traditional industry application category.

But the basic idea is similar, is to find the corresponding object, to run the corresponding method, and here the measured target is a detailed class inside a function.

Generally speaking, a story always has an opening monologue, here too. It's just not that cool, and there's no such thing as a Xing (gan) scene ...

The background of the story is very easy. Just as the autumn wind blew through the trees, the yellow leaves were generally simple and direct.

There is a need to store (non-sdcard) space in the machine itself when the user clicks on the save file and saves the specified content to the file.

And as a test of chasing (xi) (Xia), I want to make a white box directly to it. Verify that ...

Material required for the copy: Eclipse+ddms, an already rooted Android phone (be sure to root.) No root I was in the hole)

Copy opener, one of the loading replicas:

The last little boss who needs to kill the copy is here, go to the Dungeon Room and view the dungeon scene Details:

Level is limited. Just to brush a little boss room first, do not blame. Do not abandon, only to experience the fun, not too (Zuo) attention to detail (SI) ~ ~

Copy the brush and start preparing murderous:

In the measured project, the corresponding Androidmainfest is added

Pay attention to the location of the kill, kill the location is not correct, everything is wasted ~

<uses-library android:name= "Android.test.runner"/>---------to introduce the dependent libraries required for Android unit testing

Instrumentation android:name = "Android.test.InstrumentationTestRunner" android:targetpackage= " Com.example.fileoper "

Each of them is the corresponding key material required for the kill item to be used and the corresponding kill copy name

Preparations are almost the same. Can start to kill the small boss, just see then clapped,,, a white light across

New out of your class. The method used to test the measured class. Watch out for new when extends

It, or you will find that after the white light fell on the little boss of the Wave sound ~ ~ ~

Then, brush the brushes, the knife sound fell. The little boss will fall. Get replica props: Android instrumentation Unit Test Small dagger.

Attack 1-10 Defense 1-10 additional properties: Magic props can be seen

In the dungeon kill process, by the small boss to engage in the small damage to the place:

1, must carry the corresponding props. Or even a little boss can kill you (Root's Android phone)

2, with good props. Remember to set the appropriate gems on the props (see if/data/data/com.example.fileoper/files is 777, you can see it in the Ddms file Explorer, and you can join the ADB shell to see it yourself.) Be sure to check the last Files folder. Let's say it's not 777, 777 in front, and you'll end up on your knees to conquer.

3, the object to be measured and the way to measure the class can be put into different packages below, import is also able to.

Also, suppose you are a man who cannot see warn. And just in the middle there's a similar

no instrumentation runner found for the launch, using 
android.test.instrumentationtestrunne r The problem, choose Project's properties, right side assume that there are repeatedly kept up-to-date. The removal replica reproduces execution to be able to

Tips: Irobotium in the beginning of the title? What's the matter with this? , it doesn't really matter much, Irobotium just uses his own solo class. In essence, there seems to be no difference with the Android.test.runner Android.test.instrumentationTestRunner here (the individual is not feeling any big difference)

Bai---Fall swallow fly first heavy Android unit test instrumentation and Irobotium