Yeah there are several reasons. Selenium is a cool framework for some situations, but if you've ever used it, you know how much of a terror it, and its associated services/drivers, are to maintain.
Our UI layer is also not a standard framework you pull off a shelf, and it's implemented as multiple frameworks that support different interaction paradigms.
UI automation is also more like a 'last resort' for when your development team builds things so poorly that nothing else works. Proper implementation of MVC/MVVM patterns allow for test injection just below the view layer, meaning automation doesn't need to care about how it looks (which it can't possibly validate anyways).
That said, Gw2 was instrumented for test automation after the game released. While we are driving most of the game just under the UI with our automation, there's still some older UI that owns business logic that it shouldn't.
Rather than working around those decisions...
Read more