search

bs00336332 / robotframework-seleniumlibrary

Automatically exported from code.google.com/p/robotframework-seleniumlibrary
Apache License 2.0
0 stars 0 forks source link

Capture Screenshot keyword captures black screen for IE #232

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Capture Screenshot keyword captures black screen for IE regardless whether the 
virtual machine and host of virtual machine are locked by screen saver or not. 
No suspicious error is noticed in selenium log. The test automation is 
triggered from Hudson.

Based on my observation, the problem did not occur when I tested the 
functionality of Capture Screenshot keyword. It started when I let the test 
automation run automatically overnight. That's when screen saver locking 
happened. However, when I reboot all the virtual machines as well at the host 
and re-execute the test, I still get black screen in the png files in all of 
the virtual machines.

Attempted to use Snapsie 0.2 in Windows 7 virtual machine with IE9 but 
encountered some abnormal errors that I forgot to capture before I reverted the 
snapshot. I suspect snapsie 0.2 is too old and no longer maintained to suit new 
version of browsers.

Robot IDE version: 
0.39.1

Robot Framework version:
2.6.3

Selenium Library version:
Installed with 2.8.1 but replace selenium-server.jar manually with 
selenium-server-standalone-2.20.0.jar (of course, it has been renamed to 
selenium-server.jar) to overcome IE browser closure issue.

Mabot version:
0.7

Operating system:
Windows XP SP3 and Windows 7 SP1 (32 bits)

Browsers:
IE7 (Windows XP virtual machine), IE8 (Windows XP virtual machine), IE9 
(Windows 7 virtual machine)

Original issue reported on code.google.com by totzi...@gmail.com on 13 Mar 2012 at 7:59

GoogleCodeExporter commented 9 years ago 
Found an old solution in 2010 using snapsie related to screen locked. Tried it 
but the abnormal behaviour in Win7 and IE9 freak me out. Anyway, my current 
case happened even when the screen is not locked.

Original comment by totzi...@gmail.com on 13 Mar 2012 at 8:04

GoogleCodeExporter commented 9 years ago 
This seems to be a bug in Selenium itself and thus something we cannot do much 
in SeleniumLibrary. Since Selenium 1.0 is nowadays deprecated the bug is not 
likely to be fixed in it. You might want to test Selenium 2 and 
Selenium2Library instead.

Original comment by pekka.klarck on 4 May 2012 at 10:12