We schedule the main thread iff:

• It has an input or
• It has an AsyncTask result/progress
  in its main queue.

When an AsyncTask onPostExecute is not overwritten, it is not instrumented. Hence, though the main thread is scheduled and the scheduler waits for notification, main thread does not notify. In that case, the test is deadlocked.

As a temporary solution, we schedule main thread only if it is waiting.
(This causes not to schedule the main thread although it has an event handler in its queue, to be scheduled when it is its turn. How can we handle that situation?)

To check if the action bar is created or not, we used to check Activity.getActionBar.
However, that causes the action bar to be created if it is null (probably before setting up the necessary structures by UI thread).
Now, we read mActionBar of android.app.Activity or android.support.v7.app.ActionBarActivityDelegate to check whether the action bar is initialized or not.

Enable InputRepeater to be scheduled only if the next event is available (its view is created, etc..)
Currently it gets scheduled but does not inject the event if it is not available.

android.app.Fragment does not exist in earlier versions. Support libraries have the class e.g. (android.support.v4.app.Fragment) that is not included in the compilation of our Ase library.
Get FragmentManager, Fragments, etc seperately using the runtime class information.

Problem:

• Two fragments view list items that use the same layout file for an item, hence same id for the views in the item view
• Replayed events: (1) move to fragment 0 from 1 (2) click on an item's checkbox
• Event might be replayed in fragment 0. Because, the fragment lifecycle events are asynchronous and an event may be repeated before inflating the selected fragment's view. The view exists on the current view hierarchy (inflated the same item view layout), and event is replayed.

Solution:

• Keep the fragment in which the view is inflated and check whether that fragment is visible before replaying the input

How:

• The fragments may not have unique ids, may not have tags. We use the class names as identifiers.
• We already instrument a view (with a recording event handler) in a fragment's layout in onCreateView of a fragment
• Record the name of the fragment inside the recorded event
• Before replaying an event:
  • Get all currently visible fragments and check if the event view's fragment matches with any of them

Currently, we traverse and instrument views in activity and fragment layouts, i.e. when an activity is created or a fragment view is created.
In ListView, views are inflated dynamically. Hence, we could not traverse inside each view.
We should instrument "getView()" method and traverse the views inside the item view. So, we can instrument each of these children views (e.g. CheckBox in an item's view in ListView)

Before finishing a test, we check whether there is a thread which is okToSchedule.
An AsyncTask is okToSchedule if it is waiting for the Scheduler to schedule it.

Problem:
The AsyncTask thread has not executed when I check it for scheduling. I finish a test when none of the threads are okToSchedule.
After the new test starts, AsyncTask waits for the Scheduler and the task of a previous test gets scheduled in the second test.

Solution:
Read the private field sPoolWorkQueue of an AsyncTask class and set okToSchedule accordingly.
Note: The name of the field in sWorkQueue in Android version < 4.0.1

We can keep the full path from root view to a particular view and check the existence of these views while repeating the inputs.

Most views do not have ids, for now, I keep Activity, Fragment, ListView ids and position in a listview.

Instrument and control onCancelled() of an AsyncTask.
(Runs on the UI thread after cancel(boolean) is invoked and doInBackground(Object[]) has finished.)