Add dependency on a mocking library #1016
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1016
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A mocking library comes handy for writing tests which exercise only a specific class or function independently of the rest of the code. This is especially useful with system functions like
os.listdir()
which works differently across platforms.On #tahoe-lafs, Zooko proposed to use the
mock
Python library written by Michael Foord.If nobody objects, I'll post a patch which add a dependency on
mock
in source:/_auto_deps.py#L1.Yeah, go ahead.
Attachment add-mock-dependency.dpatch (2057 bytes) added
Here is it.
Let's wait til we have tests that use this library and then commit the patch that adds the dependency along with the patch that uses it.
The patch has been pushed as part of work on #534 (Unicode issues in CLI) in branch ticket534.
zooko is merging the ticket534 branch.
This was done in changeset:b2542b87085be095. But I just now realized that it was done wrong!
mock
is a test-time dependency not a run-time dependency, so it should be included intests_require
in source:setup.py and excluded frominstall_requires
in source:_auto_deps.py.Attachment mock-require.dpatch (46452 bytes) added
I didn't knew about
tests_require
. That's indeed a good idea to use it.Zooko, the patch looks correct and the functionality (mock dependency is installed if unit tests are run) is working as expected so I'll close this ticket.