| 2013-07-19 11:20:41 |
Javier Collado |
description |
Reviewing the test case results for the webbrowser application in maguro:
http://10.97.0.1:8080/job/saucy-touch-maguro-smoke-webbrowser-app-autopilot/13/console
I see that all the failures there are related to the autopilot's Eventually matcher.
This means that:
- there's a race condition (unlikely because 10 seconds seems a reasonable timeout value)
- the application is misbehaving and not really performing the actions that autopilot asked it to do
- there's a communication problem between the application and the autopilot processes and the updates in the widgets aren't correctly communicated. |
Reviewing the test case results for the webbrowser application in maguro:
http://10.97.0.1:8080/job/saucy-touch-maguro-smoke-webbrowser-app-autopilot/13/console
I see that all the failures there are related to the autopilot's Eventually matcher.
This means one of:
- there's a race condition (unlikely because 10 seconds seems a reasonable timeout value)
- the application is misbehaving and not really performing the actions that autopilot asked it to do
- there's a communication problem between the application and the autopilot processes and the updates in the widgets aren't correctly communicated. |
|
