Hi,
On my project now, our test suite has reached a large enough size that
we want to run multiple test suites in parallel via hudson (we
currently only have one worker thread in the hudson build slave). In
order to do this I need to run the selenium server externally instead
of embedded but I'm having some problems with my firefox profile not
being picked up. In my project I have a src/firefox directory that
contains two files cert8.db and cert_override.txt and I have the
following TelluriumConfig.groovy
embeddedserver {
//port number
port = "4444"
//whether to use multiple windows
useMultiWindows = false
//whether to trust all SSL certs, i.e., option
"-trustAllSSLCertificates"
trustAllSSLCertificates = true
//whether to run the embedded selenium server. If false, you
need to manually set up a selenium server
runInternally = true
//By default, Selenium proxies every browser request; set this
flag to make the browser use proxy only for URLs containing
'/selenium-server'
avoidProxy = false
//stops re-initialization and spawning of the browser between tests
browserSessionReuse = false
//enabling this option will cause all user cookies to be
archived before launching IE, and restored after IE is closed.
ensureCleanSession = false
//debug mode, with more trace information and diagnostics on the console
debugMode = false
//interactive mode
interactive = false
//an integer number of seconds before we should give up
timeoutInSeconds = 30
//profile location
profile = "./src/firefox"
//user-extension.js file
userExtension = "target/test-classes/extension/user-extensions.js"
}
This works fine, however if I start up selenium externally with the
following command line;
java -jar
.m2/repository/org/seleniumhq/selenium/server/selenium-server/1.0.1-te3/selenium-server-1.0.1-te3.jar
-port 4242 -singleWindow -profilesLocation
/home/stdtest/hudson/workspace/STDTestRunner\ Cache\
Warming/FunctionalTests/src/firefox/ -trustAllSSLCertificates
and change the port and runInternally settings accordingly, I'm able
to make contact with the server however my tests just time-out as the
SSL certificate triggers a warning (due to being self-signed). I've
tried running selenium with the -debug flag to pull out the location
of the profile that is used and I can see that the profile that is
created does not contain a cert_override.txt file at all. Am I missing
some arguments in my command for starting up selenium? Why isn't it
using my profile when not running in embedded mode?
Regards,
Jonathan
--
You received this message because you are subscribed to the Google Groups
"tellurium-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tellurium-users?hl=en.
