need tests for create-{client, node} with default nodedir #1153

Open
opened 2010-08-03 04:05:04 +00:00 by davidsarah · 0 comments
davidsarah commented 2010-08-03 04:05:04 +00:00
Owner

We shouldn't create a node at the actual default basedir (which might already exist), which is why there are no existing tests for this.

However, we could:

  • check that the result of [get_default_nodedir]source:src/allmydata/scripts/common.py@4615#L10 is sensible;
  • mock get_default_nodedir to return a default nodedir under the _trial_temp directory.

To test the logic for getting the default nodedir from the registry entry on Windows, we can mock sys.platform and allmydata.windows.registry.get_registry_value.

We shouldn't create a node at the actual default basedir (which might already exist), which is why there are no existing tests for this. However, we could: * check that the result of [get_default_nodedir]source:src/allmydata/scripts/common.py@4615#L10 is sensible; * mock `get_default_nodedir` to return a default nodedir under the `_trial_temp` directory. To test the logic for getting the default nodedir from the registry entry on Windows, we can mock `sys.platform` and `allmydata.windows.registry.get_registry_value`.
tahoe-lafs added the
code-nodeadmin
major
defect
1.7.1
labels 2010-08-03 04:05:04 +00:00
tahoe-lafs added this to the 1.8.0 milestone 2010-08-03 04:05:04 +00:00
zooko modified the milestone from 1.8.0 to soon 2010-08-14 06:38:04 +00:00
tahoe-lafs added
normal
and removed
major
labels 2012-04-01 05:17:55 +00:00
tahoe-lafs modified the milestone from soon to 1.11.0 2012-04-01 05:17:55 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1153
No description provided.