FileDocCategorySizeDatePackage
ContactsFilterInstrumentation.javaAPI DocGoogle Android v1.5 Example2719Sun Nov 11 13:01:04 GMT 2007com.google.android.samples.app

ContactsFilterInstrumentation

public class ContactsFilterInstrumentation extends android.app.Instrumentation
This is an example implementation of the {@link android.app.Instrumentation} class, allowing you to run tests against application code. The instrumentation implementation here is loaded into the application's process, for controlling and monitoring what it does.

Fields Summary
Constructors Summary
Methods Summary
public voidonCreate(android.os.Bundle arguments)

        super.onCreate(arguments);

        // When this instrumentation is created, we simply want to start
        // its test code off in a separate thread, which will call back
        // to us in onStart().
        start();
public voidonStart()

        // First start the activity we are instrumenting -- the contacts
        // list.
        Intent intent = new Intent(Intent.MAIN_ACTION);
        intent.setClassName(getTargetContext(),
                "com.google.android.contacts.ContactsList");
        Activity activity = startActivitySync(intent);

        // This is the Activity object that was started, to do with as we want.
        Log.i("ContactsFilterInstrumentation", "Started: " + activity);

        // We are going to enqueue a couple key events to simulate the user
        // filtering the list.  This is the low-level API so we must send both
        // down and up events.
        sendKeySync(new KeyEvent(KeyEvent.ACTION_DOWN, KeyEvent.KEYCODE_M));
        sendKeySync(new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_M));
        sendKeySync(new KeyEvent(KeyEvent.ACTION_DOWN, KeyEvent.KEYCODE_A));
        sendKeySync(new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_A));

        // Wait for the activity to finish all of its processing.
        waitForIdleSync();

        // And we are done!
        Log.i("ContactsFilterInstrumentation", "Done!");
        finish(Activity.RESULT_OK, null);