Changes between Initial Version and Version 1 of Ticket #999, comment 19
- Timestamp:
- 2011-07-27T23:10:14Z (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #999, comment 19
initial v1 1 My current test suite contains several tests that Zooko calls "transparent box". I need to decide whether they are appropriate .1 My current test suite contains several tests that Zooko calls "transparent box". I need to decide whether they are appropriate: 2 2 3 Test 1:remote_allocate_buckets populates incoming with shnum(s)4 Test 2:an attempt to allocate the same share (same ss) does _not_ create a new bucketwriter5 Test 3:test allocated size6 Test 4:together remote_write, remote_close, get_shares, and read_share_data behave3 1. remote_allocate_buckets populates incoming with shnum(s) 4 2. an attempt to allocate the same share (same ss) does _not_ create a new bucketwriter 5 3. test allocated size 6 4. together remote_write, remote_close, get_shares, and read_share_data behave 7 7 8 Since I am altering the location (from server to backend/core) of some of this functionality, and since I am altering the mechanism by which the filesystem is manipulated (to FilePath)... I think all of these tests are necessary.8 Since I am altering the location (from server to backend/core) of some of this functionality, and since I am altering the mechanism by which the filesystem is manipulated (to !FilePath)... I think all of these tests are necessary. 9 9 10 10 It would be nice if the tests were designed to ensure the proper behavior independent of the underlying storage medium... but I think I need to assume a filesystem-like interface for at least (1,2, and 4), probably (3) as well...