We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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();
The text was updated successfully, but these errors were encountered:
You can also use the same strategy.
File cacheDir = new File(context.getCacheDir(), "volley"); Network network = new BasicNetwork(new OkHttpStack(new OkHttpClient())); // Inject asynctask executor ResponseDelivery delivery = new ExecutorDelivery(ASYNC_EXECUTOR); requestQueue = new RequestQueue(new DiskBasedCache(cacheDir), network, 4, delivery); requestQueue.start(); //set it during wasp init ... .setNetworkStack(VolleyNetworkStack.newInstance(requestQueue))
Haven't tried but should work.
Sorry, something went wrong.
No branches or pull requests
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();
The text was updated successfully, but these errors were encountered: