Result for 0BB3D019E8A9594EE744E9BCEF9C47BEFE51E772

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/fudge/tests/test_inspector.pyc
FileSize18027
MD557BDC5BE07DFF217E9D428C6ED9E2D6D
SHA-10BB3D019E8A9594EE744E9BCEF9C47BEFE51E772
SHA-25668D39F2D7106E21C6C1F03273930DBA8D550F03864506CBD12701F5D1A6BCE1F
SSDEEP384:M26LzLqrRCZIcIu/fVekTZfMqkZ7ZtWnXeiPhy86g:MR3+rRCZIcIu/fVekTZfMqkZ7ZtWnXeI
TLSHT1F0826BA0F3A7495BD6721471E2E4131BEE74F1F7EB01A781227C407A2D98399CA7A7C1
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD55B8785CBEEF93AF07A9448E5816373BA
PackageArchnoarch
PackageDescriptionComplete documentation is available at http://farmdev.com/projects/fudge/ Fudge is a Python module for using fake objects (mocks and stubs) to test real ones. In readable Python code, you declare what methods are available on your fake and how they should be called. Then you inject that into your application and start testing. This declarative approach means you don't have to record and playback actions and you don't have to inspect your fakes after running code. If the fake object was used incorrectly then you'll see an informative exception message with a traceback that points to the culprit. Here is a quick preview of how you can test code that sends email without actually sending email:: @fudge.patch('smtplib.SMTP') def test_mailer(FakeSMTP): (FakeSMTP.expects_call() .expects('connect') .expects('sendmail').with_arg_count(3)) send_mail()
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-fudge
PackageReleaselp150.2.3
PackageVersion1.1.0
SHA-160DC069A7E153DB3A9A044E2B44D3BFC28881AAF
SHA-2563BF09D5211E6497B12EA7F1A764E47AE156FA6706799D8897E1C715D063D6597
Key Value
MD5F5B77D1E78BC753A82C6DBD848B9E46B
PackageArchnoarch
PackageDescriptionComplete documentation is available at http://farmdev.com/projects/fudge/ Fudge is a Python module for using fake objects (mocks and stubs) to test real ones. In readable Python code, you declare what methods are available on your fake and how they should be called. Then you inject that into your application and start testing. This declarative approach means you don't have to record and playback actions and you don't have to inspect your fakes after running code. If the fake object was used incorrectly then you'll see an informative exception message with a traceback that points to the culprit. Here is a quick preview of how you can test code that sends email without actually sending email:: @fudge.patch('smtplib.SMTP') def test_mailer(FakeSMTP): (FakeSMTP.expects_call() .expects('connect') .expects('sendmail').with_arg_count(3)) send_mail()
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-fudge
PackageReleaselp151.3.3
PackageVersion1.1.0
SHA-118C8621522567E66C64891038C9AF50C1E61A076
SHA-256D83F07C4246563D3C12989FD6105B47E079349DC5071D4CC8027A6A50E695344