[#DWR-460] Investigate and fix broken tests in testdwr - DWR

Details

Type: Task
Status: Open
Priority: Normal
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: 3.0
Component/s: testdwr.war

Documentation Required:
No

Description:

Hide
Marshall -> Dom Element Param
Fails in all versions of IE.

Binary
Fails in all versions of IE.
Looks like this may be due to a timing issue with the iframe. The body of the iframe is not yet populated.

Opera 9
Set cookie fails
Binary Simple fails

Opera 10
In addition to the failures in version 9 - Remoting timeout
also fails.

404 Test
Broken on all browsers.

Show
Marshall -> Dom Element Param Fails in all versions of IE. Binary Fails in all versions of IE. Looks like this may be due to a timing issue with the iframe. The body of the iframe is not yet populated. Opera 9 Set cookie fails Binary Simple fails Opera 10 In addition to the failures in version 9 - Remoting timeout also fails. 404 Test Broken on all browsers.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Mike Wilson added a comment - 21/Jun/11 2:45 PM

I briefly looked at the DOM tests some time ago and IIRC it was due to something with xmlns attributes having changed their value so that the html text compare failed.

Show

Mike Wilson added a comment - 21/Jun/11 2:45 PM I briefly looked at the DOM tests some time ago and IIRC it was due to something with xmlns attributes having changed their value so that the html text compare failed.

Hide

Permalink

David Marginian added a comment - 21/Jun/11 3:28 PM

404 is failing because of the following in engine.js:

if (reply == null || reply == "") {
dwr.engine._handleError(batch, { name:"dwr.engine.missingData", message:"No data received from server" });
}
else if (status != 200) {
dwr.engine._handleError(batch, { name:"dwr.engine.http." + status, message:req.statusText });
}

reply is empty or null in case of 404 and the status != 200 block is not executed.

Show

David Marginian added a comment - 21/Jun/11 3:28 PM 404 is failing because of the following in engine.js: if (reply == null || reply == "") { dwr.engine._handleError(batch, { name:"dwr.engine.missingData", message:"No data received from server" }); } else if (status != 200) { dwr.engine._handleError(batch, { name:"dwr.engine.http." + status, message:req.statusText }); } reply is empty or null in case of 404 and the status != 200 block is not executed.

Hide

Permalink

David Marginian added a comment - 06/Mar/13 5:15 AM

Mike, since you made the changes to testdwr all the tests are running for me. Should we close this?

Show

David Marginian added a comment - 06/Mar/13 5:15 AM Mike, since you made the changes to testdwr all the tests are running for me. Should we close this?

DWR

Investigate and fix broken tests in testdwr

Details

Activity

People

Dates