testbrowser gives unhelpful errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 3 |
Won't Fix
|
Medium
|
Unassigned | ||
zope.testbrowser |
Invalid
|
Low
|
Unassigned |
Bug Description
Every now and then when something goes wrong (server error), zope.testbrowser gives this confusing error message instead:
Failed example:
browser.
Exception raised:
Traceback (most recent call last):
File ".../zope3/
File "<doctest demo.txt[11]>", line 1, in ?
File ".../zope3/
File ".../zope3/
return self.open(
File ".../zope3/
return self._mech_
File ".../zope3/
File ".../zope3/
response = upgrade_
File ".../zope3/
data = get_data()
File ".../zope3/
return self.read(-1)
File ".../zope3/
File ".../zope3/
TypeError: 'NoneType' object is not callable
I think I saw this one reported a while ago, but I cannot find the issue in the collector.
Changed in zope.testbrowser: | |
importance: | Undecided → Medium |
Changed in zope3: | |
status: | New → Won't Fix |
Changed in zope.testbrowser: | |
assignee: | nobody → Benji York (benji-york) |
importance: | Medium → Low |
status: | New → Triaged |
Changed in zope.testbrowser: | |
assignee: | Benji York (benji) → nobody |
I've seen this before, and have a vague feeling that I fixed it (or at least looked at it).
What version(s) of testbrowser do you see this in? Can you demonstrate how to reproduce it?