Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

consider using pytest-mock #42

Closed
heartsucker opened this issue Oct 17, 2018 · 0 comments · Fixed by #62
Closed

consider using pytest-mock #42

heartsucker opened this issue Oct 17, 2018 · 0 comments · Fixed by #62

Comments

@heartsucker
Copy link
Contributor

I find that this generally cleans up test code quite a bit and makes it more readable. (pretty sure @redshiftzero zero introduced me to it :D )
@heartsucker heartsucker mentioned this issue Oct 24, 2018
Merged
legoktm pushed a commit that referenced this issue Dec 11, 2023
@redshiftzero
Merge pull request #42 from pierwill/edit-readme-qrexec
2516d18 
Edit qrexec policy instructions in README
legoktm pushed a commit that referenced this issue Dec 15, 2023
@redshiftzero
Merge pull request #42 from freedomofpress/parse-reply-uuid
2c13513 
Parse reply UUID
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

converted tests to use pytest-mock freedomofpress/securedrop-client
1 participant
@heartsucker