[Twisted-Python] Another brown paper bug release.
glyph at twistedmatrix.com
Wed May 9 04:16:09 EDT 2001
On Wednesday 09 May 2001 00:19, you wrote:
> Random note: web.Resource and friends and web.Request do not rely on an
> internet connection: they rely on a handler which has a .server with some
> properties and some other attributes. Creating such a handler is no problem
> if we start from FileWrapper, add attributes, and create a server and
> attach it to the handler ourselves.
> So any *recorded and analysed* bug should be able to quickly become a test
While this is true in theory, there are many practical concerns that can't be
simulated by an automatic test case; the one outstanding bug is one of these.
Since twisted.web relies on external processes -- for server distribution,
for CGI scripts -- race conditions may arise that are impossible to unit
test. So, we need some functional testing as well, to make sure that those
sorts of conditions don't arise.
If anyone else can think of a way to get fork() into a unit test, I'd like to
hear about it :). But, even more than that, I am frequently surprised when I
try to run "working" code on Windows or Jython and have it crash due to some
undocumented incompatibility (or even a documented one that I just haven't
I'm a big proponent of automated testing, though, so I'd love to be wrong.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
More information about the Twisted-Python