| Re: [jubula-rc-dev] Webdriver AUT Agent |
|
Hello Dave,
we are ourselves also interested in switching Jubulas HTML RC part to a Webdriver based approach - see [1].
The current implementation is hosted publicly @bitbucket - see [2]. I think the current implementation might be a good starting point.
Keep in mind that the AUT-Agent itself is not responsible for the remote controlling part - it's simply invoking - see [3] - and monitoring the AUTs process (which is for the HTML toolkit an AbstractStartPseudoJavaAUT).
Best regards, Markus Tiede
[1] http://bugzilla.bredex.de/1399#c2 -- BREDEX GmbH Mauernstr. 33 38100 Braunschweig
Tel.: +49-531-24330-0 Fax: +49-531-24330-99 http: www.bredex.de
Geschäftsführer: Andreas Vogel, Ulrich Obst, Achim Lörke Amtsgericht Braunschweig HRB 2450 Von: jubula-rc-dev-bounces@xxxxxxxxxxx <jubula-rc-dev-bounces@xxxxxxxxxxx> im Auftrag von Dave Ball <d.ball@xxxxxxxxxxxx>
Gesendet: Samstag, 14. Februar 2015 18:10 An: jubula-rc-dev@xxxxxxxxxxx Betreff: [jubula-rc-dev] Webdriver AUT Agent Hi,
I am interested in writing an AUT Agent that uses webdriver APIs directly, rather than through selenium. Eventually I want to use this for testing a Vaadin based app across a number of target platforms. I have had a play and produced a very hacked together experiment as a learning exercise, but now planning to start from scratch with a (hopefully) properly structured implementation. So to help me kick this off, is this something anyone has looked into in the past, and do you have any suggestions on the best way to start, or ideas i should look to incorporate? Many thanks, Dave
|