Thanks to visit codestin.com
Credit goes to github.com

Skip to content

How to test Android UI using IdlingResource(Espresso) when using Wasp network requests #132

@ghost

Description

Hi Orhan Abi,

Espresso is waiting for AsyncTask on network calls. Is it possible to do it on Wasp? There is same problem on Retrofit link below.

http://stackoverflow.com/questions/23142437/how-to-test-android-ui-using-idlingresource-when-using-retrofit-network-requests

Retrofit can do it.
The most straightforward solution for this: is to basically swap out Retrofit's Thread-pool executor with an AsyncTask one.

new RestAdapter.Builder()
.setEndpoint(LOCLSET_SERVER_URL)
.setExecutors(AsyncTask.THREAD_POOL_EXECUTOR,
new MainThreadExecutor())
.build();

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions