Some scenario are consistently failing on Travis CI

[ericcornelissen]

• Parent issues: -
• Relevant issues: -
• Estimated effort: 5 hours

---

What

I gathered a list of androidTests that seem to be consistently failing when they're ran on Travis CI (based on reviewing ~10 builds).

• One test related to the ChangeContactActivity seems to be failing rather consistently:

Feature Change contact activity > Scenario Outline Change the name of a contact[test(AVD) - 5.1.1] FAILED 
	android.support.test.espresso.PerformException: Error performing 'replace text' on view 'with id: com.nervousfish.nervousfish:id/edit_contact_name_input'.
	at android.support.test.espresso.PerformException$Builder.build(PerformException.java:83)

• Another test related to the ChangeContactActivity that frequently fails is the "Press the back button after editing the contact" scenario:

Feature Change contact activity > Scenario Outline Press the back button after editing the contact[test(AVD) - 5.1.1] FAILED 
	java.lang.RuntimeException: Could not launch intent Intent { flg=0x10000000 cmp=com.nervousfish.nervousfish/.activities.ChangeContactActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1497793680504 and now the last time the queue went idle was: 1497793725155. If these numbers are the same your activity might be hogging the event queue.
	at android.support.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:360)

Why

This issue is needed for the project because it improves the certainty the app is working correctly.

How

Not sure 😕 any ideas are welcome. Some possible causes:

• Can't find the view
• App doesn't work on older phones

Definition of ready

This features is not ready until the following issues are finished:

• Waiting on other issues is not needed

Definition of done

This task can be considered done when:

• The scenario outline "Change the name of a contact" doesn't fail (as often) on Travis CI.
• The scenario outline "Press the back button after editing the contact" doesn't fail (as often) on Travis CI.

Notes

If you find any other scenarios that always seem to fail, and always for the same reason, be sure to comment them on this issue and I will add them to the list 🙂