The QA team spoke about this at length. The take-home points are: 1) This is almost certainly a bug in the test cases, rather than in autopilot itself. The fact that the issue exists independant of the autopilot version seems to confirm this. Unless anyone objects, I'm going to remove the bug task against autopilot, and add one for the actual applications that are failing.
2) The root cause here is that the tests are written poorly. Specifically, they don't fail well. Many tests are writtenn such that they have a bunch of actions, and then assertions at the end of the test case. This is best practise for *unit* tests, but does not work well in an acceptance test where the test code and applicaiton code are completely asynchronous of each other. 3) Leo is slowly converting existing acceptance test suites to the page object pattern (http://code.google.com/p/selenium/wiki/PageObjects) which allows a greater level of abstraction, and should allow better failure messages. This process will likely help situations like this in the future. 4) balloons is going to blog about the page object conversion process, so hopefully it won't be just Leo doing the conversion, which should speed things up a bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284316 Title: multiple StateNotFoundError failures in image 206 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1284316/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
