Marc Weber
Personally I would stick with one of the bindings supported by the core selenium dev team, you can be fairly sure that they will be subject to active development and that support isn’t going to tail off at any point in the near future.
I can see some advantages in suggesting you use the same programming language as the dev team but I would counter that with a couple of questions:
· How often does the core dev team help you write your tests (if never why would they suddenly start writing them now)?
· Is a Java implementation really going to be that hard for professional software developers to understand?
I would suggest that the majority of work is going to be using the selenium API which is pretty easy to pick up (yay for auto complete in IDE’s) so any dev worth their salt should really have no problems. The bit that is going to take longest is writing the test framework. Below is a link to my current one on github, I’m sure there are others knocking around as well (the selenium blog is a good place to look) so you can probably find something that meets your requirements with a bit of digging.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/48W35zg34HwJ.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
I'll take a look at your framework (thank you!), and have another chat
to the dev manager shortly to see if I can change his mind....
Cheers,
Ellie
On Dec 20, 9:20 am, "Mark Collin" <m...@ardescosolutions.com> wrote:
> Personally I would stick with one of the bindings supported by the core
> selenium dev team, you can be fairly sure that they will be subject to
> active development and that support isn't going to tail off at any point in
> the near future.
>
> I can see some advantages in suggesting you use the same programming
> language as the dev team but I would counter that with a couple of
> questions:
>
> . How often does the core dev team help you write your tests (if
> never why would they suddenly start writing them now)?
>
> . Is a Java implementation really going to be that hard for
> professional software developers to understand?
>
> I would suggest that the majority of work is going to be using the selenium
> API which is pretty easy to pick up (yay for auto complete in IDE's) so any
> dev worth their salt should really have no problems. The bit that is going
> to take longest is writing the test framework. Below is a link to my
> current one on github, I'm sure there are others knocking around as well
> (the selenium blog is a good place to look) so you can probably find
> something that meets your requirements with a bit of digging.
>
> <https://github.com/Ardesco/Ebselen>https://github.com/Ardesco/Ebselen
>
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
ebselen-tests should have two xls files under the test folder which are used
in test tree and one css file used in the main tree.
The CSS file is used by the HTML report generated by the tests when they are
run and the xls files are used in the data driven test examples.
You don't need the xls files if you delete the website.google and
pagefactory.google packages. If you delete the CSS file the test reports
generated by tests tagged with the @SeleniumTest annotation will have no
styling.
-----Original Message-----
From: seleniu...@googlegroups.com
[mailto:seleniu...@googlegroups.com] On Behalf Of Ellie Lock
--
You received this message because you are subscribed to the Google Groups
"Selenium Users" group.
It will be slower at first but in the long run it's much quicker.
-----Original Message-----
From: seleniu...@googlegroups.com
[mailto:seleniu...@googlegroups.com] On Behalf Of emily
Sent: 21 December 2011 15:48
To: Selenium Users
Hi Ellie
Emily
No I’m not seeing that…
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/-KELDknft_sJ.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
> the IDE, but we found that exporting as an XML file was easier for us,
> and we simply parse through that on our dashboard and turn the IDE
> commands into Webdriver commands.
So you are not using Selenium 2.0? I haven't been able to find any
documentation on how to connect from the IDE to 2.0. . .
> Here are a few links that may help you with the exporting in different
> formats:
> https://addons.mozilla.org/en-US/firefox/addon/selenium-ide-php-formatters/
> https://addons.mozilla.org/en-US/firefox/addon/selenium-xml-formatter/
>
> Hope that this helps you, anything to help make it easier and take
> less time for you!
Me too, I suspect -- what are you using to get from your parsed XML to
WebDriver?
> At the beginning we were writting our own tests manually, but once we
> found the IDE we didnt look back! :-)
I'm still stuck with a manual setup, based on the Kolczynski php
interface, plus my own shims to make it work pretty seemlessly with
more basic simpletest unit tests of my app's underlying PHP.
If you or anyone else has a pointer to some basic documentation on the
relationship between the JSON wire protocol and IDE output, that would
be hugely helpful. . . As far as I can see, the IDE has access to
some functionality which simply isn't exposed via the wire protocol,
which makes me think I must be missing something.
ht
--
Henry S. Thompson, Markup Systems Ltd.
Cavers Garden Farm, Denholm; by Hawick; TD9 8LN
+44 (0) 7866 471 388
Fax: (44) 131 651-1426, e-mail: h...@markup.co.uk
URL: http://www.markup.co.uk/
[mail really from me _always_ has this .sig -- mail without it is forged spam]