[prev in list] [next in list] [prev in thread] [next in thread] 

List:       selenium-commits
Subject:    [Selenium-commits] [JIRA] Commented: (SEL-173) SeleneseRunner
From:       "Dan Fabulich (JIRA)" <jira () public ! thoughtworks ! org>
Date:       2005-12-16 6:11:59
Message-ID: 82295265.1134713519845.JavaMail.oqa-j2ee () openqa01 ! managed ! contegix ! com
[Download RAW message or body]

    [ http://jira.openqa.org/browse/SEL-173?page=comments#action_12576 ] 

Dan Fabulich commented on SEL-173:
----------------------------------

Oops!  I had actually tested this on NS7, not on IE6... if I *had* tested it on IE6, \
I would have seen that it was locking up the browser because we're usyng \
XmlHttpRequest synchronously (SJAX instead of AJAX).  SJAX is evil evil evil, because \
it utterly locks up the browser.  \
http://ajaxblog.com/archives/2005/05/25/synchronous-requests-bad

I have a patch for this (switching the SeleneseRunner to AJAX instead of SJAX) which \
I'll attach to the bug once I can attach things to bugs in the new system!

> SeleneseRunner doesn't post back results when a test fails
> ----------------------------------------------------------
> 
> Key: SEL-173
> URL: http://jira.openqa.org/browse/SEL-173
> Project: Selenium
> Type: Bug
> Components: SeleneseRunner
> Versions: 0.6
> Environment: IE6 with the Java 0.6.0 Driver (with Nelson's patch, SEL 168) on \
>                 Windows 2003
> Reporter: Dan Fabulich

> 
> 
> Add a test to RealDealIntegrationTest that should fail.  For example:
> public void testFailure() {
> try {
> selenium.verifyText("linkxxx", "This text doesn't appear on the page!");
> fail("No exception was thrown!");
> } catch (SeleniumException se) {
> assertTrue("Exception message isn't as expected", se.getMessage().indexOf("linkxxx \
> not found") != -1); }
> }
> The browser will halt execution when the test fails; it won't post back the \
> failure.  The driver side eventually times out with a \
> SeleniumCommandTimedOutException, instead of the results of the failed \
> verification. To fix this, a change is needed in SeleniumRunner.html.  One change \
> is needed to ensure that the final message is reliably posted back; another change \
> is needed to ensure that that, if there's a Selenium bug, that message will be \
> returned as well. 75c75,78
> <     testLoop.testComplete = function() {window.status = "Selenium Tests Complete, \
>                 for this Test"};
> ---
> > testLoop.testComplete = function() {
> > window.status = "Selenium Tests Complete, for this Test";
> > this.continueCurrentTest(); // Continue checking for new results
> > };
> 171c174
> <     postResult = "ERROR"
> ---
> > postResult = "ERROR: " + message;

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
Selenium-commits mailing list
Selenium-commits@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-commits


[prev in list] [next in list] [prev in thread] [next in thread]