Testing onActivityResult for specific requestCode

Question

I've seen an answer that gets really close to solving my question: https://stackoverflow.com/a/13060588/1481760

I'm looking to create an ActivityInstrumentationTestCase2 that tests onActivityResult for various values of "requestCode".

google -> onActivityResult -> http://developer.android.com/training/basics/intents/result.html — Damien R., Feb 11 '14 at 08:31

score 0 · Answer 1 · answered Feb 11 '14 at 08:33

0

From Android Doc

@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
    // Check which request it is that we're responding to (THIS IS WHAT YOU ARE LOOKING FOR)
    if (requestCode == PICK_CONTACT_REQUEST) {
        // Make sure the request was successful
        if (resultCode == RESULT_OK) {


        }
    }
}

answered Feb 11 '14 at 08:33

Damien R.

3,383
1
21
32

I should have been more clear. I'm looking to create an ActivityInstrumentationTestCase2 that tests onActivityResult for various values of "requestCode". – Nick Feb 11 '14 at 08:38

InnocentKiller · Answer 2 · 2014-02-11T08:40:03.757

You can use it like below,

protected void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);

        if (resultCode == Activity.RESULT_OK) {
            switch (requestCode) {
            case CAPTURE_AUDIO:
                 //your code for audio result
            break;

            case CAPTURE_VIDEO:
                // your code for video result
                break;

            default:
                break;
            }
        }
    }

score 0 · Answer 3 · answered Feb 11 '14 at 08:37

When you use the below method.request code is userdefine you can specify here any number.

 startActivityForResult(i, requestCode);

and you receive the same requestCodeon the below method at argument requestCode.

protected void onActivityResult(int requestCode, int resultCode, Intent data) { }

score 0 · Accepted Answer · answered Feb 12 '14 at 06:29

My mistake... In my test case I forgot to trigger the code that actually uses startActivityForResult. I corrected that and as expected this caused onActivityResult to be called. Allowing me to test onActivityResult with various values of requestCode.

One tip- remember that the second parameter (the timeout) for waitForMonitorWithTimeout is in milliseconds not seconds as the documentation suggests.

Testing onActivityResult for specific requestCode

4 Answers4