From: nejucomo Date: Wed, 30 Jan 2008 09:45:54 +0000 (-0700) Subject: tahoe_fuse: system tests: Update comments. X-Git-Tag: allmydata-tahoe-0.8.0~167 X-Git-Url: https://git.rkrishnan.org/components/com_hotproperty/%22doc.html/architecture.txt?a=commitdiff_plain;h=ab3d399ac7e75bb745532cdd30e4b043beb8529d;p=tahoe-lafs%2Ftahoe-lafs.git tahoe_fuse: system tests: Update comments. --- diff --git a/contrib/fuse/runtests.py b/contrib/fuse/runtests.py index b55673dd..cbe18e14 100644 --- a/contrib/fuse/runtests.py +++ b/contrib/fuse/runtests.py @@ -1,11 +1,17 @@ #! /usr/bin/env python ''' -Unit tests for tahoe-fuse. - -Note: The API design of the python-fuse library makes unit testing much -of tahoe-fuse.py tricky business. +Unit and system tests for tahoe-fuse. ''' +# Note: It's always a SetupFailure, not a TestFailure if a webapi +# operation fails, because this does not indicate a fuse interface +# failure. + +# TODO: Test mismatches between tahoe and fuse/posix. What about nodes +# with crazy names ('\0', unicode, '/', '..')? Huuuuge files? +# Huuuuge directories... As tahoe approaches production quality, it'd +# be nice if the fuse interface did so also by hardening against such cases. + # FIXME: This framework might be replaceable with twisted.trial, # especially the "layer" design, which is a bit cumbersome when # using recursion to manage multiple clients.