I have already tried, and this was my last resort. In both cases I think we'd need a dev to modify the app to make it more testable. As you point out, the Browser app is going to change considerably, so I don't see the value in spending more time on this.

I did discuss an expected condition class with Andreas for an element that's stopped moving. We feel it could be worthwhile adding if there's value to it (it would avoid reimplementing it whenever it's needed) but I would be concerned that it would be overused when we should be waiting for something more specific.