@@ -11,9 +11,6 @@ Table Of Content:
1111* This will become a table of contents (this text will be scraped).
1212{: toc }
1313
14- Installation
15- ============
16-
1714General
1815=======
1916
@@ -172,19 +169,6 @@ Launching the Hub and the Remote Controls
172169 [ build your own Selenium Grid distribution from source] ( http://selenium-grid.openqa.org/build_it_from_source.html )
173170 as the fix in already checked-in in the codebase.
174171
175- Configuring the Demo
176- ====================
177-
178- How to setup the EC2 account for Amazon Web Services
179- ----------------------------------------------------
180-
181- How to deploy the demo to the Amazon Web Services
182- -------------------------------------------------
183-
184- How to run the demo in the EC2 enviroment
185- -----------------------------------------
186-
187-
188172Running the Examples Included in Selenium Grid Distribution
189173===========================================================
190174
@@ -213,24 +197,6 @@ Running the Examples Included in Selenium Grid Distribution
2131974 . Launch the tests with: ` rake tests:run_in_parallel `
214198
215199
216- HTTPS
217- -----
218-
219- > We have a client where application is built on HTTPS. We tried testing using selenium but its not supporting.
220- >
221- > Can you please suggest us the approach to be followed to test HTTPS URL’s.
222-
223- http://blog.thirstybear.co.uk/2008/05/selenium-and-https.html
224-
225- However, in some cases, you may be required to test more than one domain at
226- once. The most common case is when you need to test both http://blah.com and
227- https://blah.com . "http:" and "https:" are considered different "origins" from
228- JavaScript perspective, so tests running on one can't run on the other. In
229- that case, for now, you'll have to use one of our experimental browser
230- launchers which support running in multiple domains. (Also be sure to read the
231- HTTPS section of this documentation for more details about HTTPS support.)
232-
233-
234200Running Your Tests Against Selenium Grid
235201========================================
236202
@@ -360,25 +326,62 @@ I have some test cases and I want to run them against Selenium Grid, what do I n
360326 which [ include HTML capture and OS screenshots when a test
361327 fail] ( http://ph7spot.com/examples/rspec_report/index.html ) .
362328
363- My test cases are in HTML (Selense), how can I run those against Selenium Grid ?
364- ------------------------------------------------------------------
329+ My test cases are in HTML (Selenese), how can I run those against Selenium Grid ?
330+ ------------------------------------------------------------------
331+
332+ You would need a parallel test runner for Selenium Grid.
333+
334+ I might eventually end up working on such a parallel test runner for HTML
335+ test suites, nevertheless my time is limited and this feature is quite low
336+ in my priority list: in my experience HTML test suites are a nightmare
337+ to maintain you are better off writing and refactoring real code by the time
338+ your test suite grows big enough that it takes too long to run.
339+
340+ This said, there might be hope as some guys seem to be working on it though: see
341+ [ this thread] ( http://clearspace.openqa.org/thread/11482 )
342+
343+ My test is not working when I use HTTPS!
344+ ----------------------------------------
345+
346+ > We have a client where application is built on HTTPS. We tried testing using selenium but its not supporting.
347+ >
348+ > Can you please suggest us the approach to be followed to test HTTPS URL’s.
349+
350+ http://blog.thirstybear.co.uk/2008/05/selenium-and-https.html
351+
352+ However, in some cases, you may be required to test more than one domain at
353+ once. The most common case is when you need to test both http://blah.com and
354+ https://blah.com . "http:" and "https:" are considered different "origins" from
355+ JavaScript perspective, so tests running on one can't run on the other. In
356+ that case, for now, you'll have to use one of our experimental browser
357+ launchers which support running in multiple domains. (Also be sure to read the
358+ HTTPS section of this documentation for more details about HTTPS support.)
359+
360+ I get some strange errors when I run multiple Internet Explorer instances on the same machine
361+ ---------------------------------------------------------------------------------------------
362+
363+ Selenium Grid does not officially support running multiple Internet
364+ Explorer on a _ single_ Windows machine. This is mostly because:
365365
366- You would need a parallel test runner for Selenium Grid.
366+ * People who know IE better than I do (Dan Fabulich) tell me that if
367+ you run 2 browsers as the same user in HTA mode they end up sharing a
368+ singleton instance in memory, which could cause problems.
367369
368- I might eventually end up working on such a parallel test runner for HTML
369- test suites, nevertheless my time is limited and this feature is quite low
370- in my priority list: in my experience HTML test suites are a nightmare
371- to maintain you are better off writing and refactoring real code by the time
372- your test suite grows big enough that it takes too long to run.
370+ * The ` *iexplore mode ` is changing the registry settings at each
371+ session start/end to have IE use a specific Remote Control as HTTP
372+ proxy. If you run multiple Remote Controls at the same time you can
373+ see the problems coming! ;-)
373374
374- This said, there might be hope as some guys seem to be working on it though: see
375- [ this thread ] ( http://clearspace.openqa.org/thread/11482 )
375+ ** Currently, the only robust solution for running multiple IE instances
376+ with Selenium Grid is to use virtualization. **
376377
378+ This said, I am not satisfied wit the current state of affairs and I
379+ am currently working on better support for IE in Selenium Grid 1.2.
377380
378381Analysing Failures
379382==================
380383
381- When we test the applicaiton with Selenium Grid, we get nondeterministic results
384+ When we test the application with Selenium Grid, we get nondeterministic results
382385 --------------------------------------------------------------------------------
383386
384387> Locally, when we test the application with Selenium Grid, we get
0 commit comments