Closed GoogleCodeExporter closed 8 years ago
Same bug with Firefox/6.0 (Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101)
Original comment by andrew.p...@gmail.com
on 18 Aug 2011 at 3:18
Subsequent versions of Firefox also suffer from the same problem, e.g.:
Firefox 9.0 Mac OS: Run 3 tests (Passed: 1; Fails: 1; Errors 1) (1,00 ms)
MsgTest.test should log error message passed (0,00 ms)
[LOG] Caught error: TypeError An error occurred
MsgTest.test should fail with message failed (1,00 ms): AssertError:
AssertError:
MsgTest.test should throw error error (0,00 ms): :
:
Original comment by szafra...@gmail.com
on 22 Aug 2011 at 2:29
I have debugged the issue and found that there is a problem in
TestRunnerPlugin.js (which is the source for runner.js in the browser)around
line 154. The error object has a field message which contains the correct text,
but this field is not accessible through for(k in e) and hence the JSON
serialization skips it. I have attached a screenshot from the debugging session.
Please, treat this issue with high priority, because it is breaking the
developer workflow. E.g. one has to debug to see where the error comes from
instead of just looking at the message.
Original comment by pavel.ge...@gmail.com
on 15 Sep 2011 at 9:13
Attachments:
I could not resist and debugged it a bit more. I guess that for some reason on
Chrome 14 and Firefox 6 some properties become non-enumerable and hence don't
show up in the for(k in e) output. If I do:
Object.defineProperty(e, "message", {enumerable: true})
while debugging at the same line, then the for(k in e) correctly displays the
message property too.
Hope it helps
Original comment by pavel.ge...@gmail.com
on 15 Sep 2011 at 9:46
Could be related to this issue:
http://code.google.com/p/chromium/issues/detail?id=85755
Original comment by pavel.ge...@gmail.com
on 15 Sep 2011 at 9:50
At rev 1037, explicit enumeration. Need a robust Json serializer that handles
non-enumerated types and cyclical object graphs.
Original comment by corbinrs...@gmail.com
on 21 Sep 2011 at 7:55
Is this fix included in the Eclipse plugin 1.1.1e?
I don't see any failure messages in Eclipse with plugin 1.1.1e.
Original comment by jonas.ba...@gmail.com
on 30 Nov 2011 at 12:49
Original issue reported on code.google.com by
meyer...@gmail.com
on 16 Aug 2011 at 7:24Attachments: