Repository navigation
Xebium iexplore got error message "JavaScript error (WARNING: The server did not provide any stacktrace information)" #131
Description
fitnesse table is
|script |selenium driver fixture |
|start browser|iexplore|on url |http://nzakl20sv273:9081/ |
|do |open |on |/iBuilderBRC_Test |
|ensure |do |assertVisible |on|id=username |
|ensure |do |waitForVisible|on|!-id=password-!|with|fgd |
|ensure |do |type |on|id=username |with|CSOTL_3001|
|ensure |do |type |on|id=password |with|CSOTL_3001|
|ensure |do |clickAndWait |on|css=input.submit |
steps
|script |selenium driver fixture |
|start browser|iexplore|on url |http://nzakl20sv273:9081/ |
|do |open |on |/iBuilderBRC_Test |
|ensure |do |assertVisible |on|id=username |
|ensure |do |waitForVisible|on|!-id=password-!|with|fgd |
are passed
get error message for steps
|ensure |do |type |on|id=username |with|CSOTL_3001|
|ensure |do |type |on|id=password |with|CSOTL_3001|
|ensure |do |clickAndWait |on|css=input.submit |
error message is "EXCEPTION:java.lang.AssertionError: com.thoughtworks.selenium.SeleniumException: JavaScript error (WARNING: The server did not provide any stacktrace information)
"
use Firefox no any problem for above table.
can anyone tell me why I will get this error message
Activity
raboof commentedon Jun 27, 2014
Do you also see a javascript error when you perform these actions manually from IE?
yujiayujia6 commentedon Jun 27, 2014
No, we do manual test for this system many times, before we try to do automation testing. Thank you for replay.
raboof commentedon Jun 27, 2014
Well, the fact that you've done manual testing (and that it works functionally) doesn't mean there's no javascript errors in the console. Have you checked?
yujiayujia6 commentedon Jun 27, 2014
I also use following code in eclipse to test all actions are passed and no javascript error in console.
WebDriver driver;
driver = new InternetExplorerDriver;
driver.findElement(By.id("username")).sendKeys("CSOTL_3001");
driver.findElement(By.id("password ")).sendKeys("CSOTL_3001");
driver.findElement(By.id("submit ")).click();
eskape commentedon Jun 28, 2014
This is (probably) one of the reasons why we're moving to "full" webdriver implementation. Work in progress. Thanks for sharing another example.
raboof commentedon Jun 28, 2014
As Kishen Simbhoedatpanday (@eskape) correctly mentions, depending on what's actually going wrong it could be that this issue does not occur when using the 'fast selenium emulation' implementation which is now the default in newly built 0.13-SNAPSHOT versions.
If you're feeling adventurous you're welcome to build that one and try if it helps. This might well introduce some other issues, but I'd be happy to work with you to help resolve those.