[tahoe-lafs-trac-stream] [tahoe-lafs] #68: implement distributed introduction, remove Introducer as a single point of failure
tahoe-lafs
trac at tahoe-lafs.org
Fri Feb 17 16:33:43 UTC 2012
#68: implement distributed introduction, remove Introducer as a single point of
failure
-------------------------+-------------------------------------------------
Reporter: lvo | Owner: zooko
Type: | Status: assigned
enhancement | Milestone: soon
Priority: major | Version: 0.2.0
Component: code- | Keywords: scalability availability
network | introduction gsoc docs anti-censorship test-
Resolution: | needed
Launchpad Bug: |
-------------------------+-------------------------------------------------
Comment (by zooko):
killyourtv: cool! Thank you for the note. If I recall correctly, Faruq's
patch didn't have a thorough unit test.
I've noticed several good contributions to Tahoe-LAFS that are blocked on
not having unit tests. I think a lot of people know how to write Python
code but aren't sure what we expect in terms of testing, or don't know how
to use trial's features to test results that are deferred until a
subsequent event. I've been thinking that having a "unit test tutorial"
party could be fun, where everyone who has a patch for Tahoe-LAFS that
needs tests comes to the IRC channel and we pick one and walk through how
to write tests for it...
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68#comment:88>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list