@Nathan Willis Selenium requires that a) your client be a web application and b) that all clients have the same interface, right? How would that work for an android application? How would it work if you wrote a Selenium script, and then someone wrote a web application with a completely different UI?
@cwebber@identi.ca I've used it for android applications before. There's an Android driver for it. It fires up an emulator and then looks for elements with names or strings. The same set of tests can test both web and android versions of an application. Usually done by the creator of the application, though.
Kevin Everets at 2017-04-13T14:37:56Z
Christopher Allan Webber likes this.
Aha... but that doesn't change that to write tests that can be used by any client, we'd have to dictate what that interface of that client looks like, basically...
Also selenium can't drive my emacs client, or the equivalent of the pump.io "p" command line client! These interfaces are just too different to hand one test suite that will fit all of them. We could provide hooks, but that would mean asking developers to wire up a lot of manual things, which is a different kind of "interactive". We chose the route we're going down because it's something that will take the least amount of effort for developers to interface with.