yanne / api-testing

I am using this to test GitHub API
1 stars 0 forks source link

Support for Seleniumlibrary and other external libs #330

Open yanne opened 10 years ago

yanne commented 10 years ago

None

This issue was originally opened at Google Code on Mar 17, 2011.

yanne commented 10 years ago

Original comment by dietrich...@googlemail.com on Mar 17, 2011.

There is a similar issue here, but it is a general problem: How to get needed libraries during a maven build:

https://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=132

Can we use easy_install somehow.

yanne commented 10 years ago

Original comment by dietrich...@googlemail.com on Mar 17, 2011.

Or maybe -XBootclasspath? See https://code.google.com/p/robotframework/wiki/JavaIntegration#Using_additional_Java_libraries

yanne commented 10 years ago

Original comment by dietrich...@googlemail.com on Mar 17, 2011.

How about --pythonpath support?

I've managed to package the seleniumlibrary with rf, following the description by Laurent Carbonneaux https://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=132#c6 , now I can call the selenium tests with server startup and shutdown like this:

\src\test\resources>java -cp robotframework-selenium-2.5.6.jar org.robotframework.RobotFramework

For this setup, selenium-server.jar has to be in resources/lib, but need not be in the rf+selenium jar (although Laurent says you should only add the py files, he lists the selenium-server.jar as content file of the combined rf+sel jar, which seems not to work)

So far so good, however, what about other libs? I wonder if the rf commandline option -P might be helpful and why it is not supported by the jybot goal. Are there any known issues with the --pythonPath option?

yanne commented 10 years ago

Original comment by eero.hel...@gmail.com on Mar 19, 2011.

Having Selenium library included in this plugin would be absolutely fantastic.

I tried bundling Selenium Library into the Maven plugin using Mr Carbonneaux’s instructions and it seemed to work perfectly, so that works as an intermediate solution. Of course, it’d be even better if Selenium library were included in the standard distribution of the plugin.

As far as I can see, the Selenium server doesn’t necessarily need to be included, either, because you can use the Selenium Maven Plugin ( http://mojo.codehaus.org/selenium-maven-plugin/ ) to start the server in the pre-integration-test phase, run your Robot test cases in the integration-test phase, and stop the server in post-integration-test phase.

Either way, many thanks for creating the plugin; I’m already finding it extremely useful!

yanne commented 10 years ago

Original comment by mrmall...@gmail.com on Mar 20, 2011.

didn't put python path flag as I haven't personally tested it. will check it out if it works. otherwise, i'll try to put a hook somewhere so that other libraries could be used.

i'm targeting 1.1 release within the week. hopefully this should make it