Result for 086E644DE381825A423DB8E6BFCFF80D3C167D03

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/fudge/tests/test_registry.pyo
FileSize6301
MD5B73A3ACFE630E305AB58436AFD226E3F
SHA-1086E644DE381825A423DB8E6BFCFF80D3C167D03
SHA-256C2C460F979B1A42E4A2F5459A16DDBC815972134FEE42DE6348CB41AC03DC5C3
SSDEEP96:weaMmRMX/BaR2mmDe9V/9dvaiiqzi/9gC5va8/R95Ajl4ZCDEyN0osSFv0QE9Row:naFGPeF5j6OF8Z8/k
TLSHT127D1BD81E3E7854BCAA0697694F01307DDB2F1F366016B4266FCE4BD2D98355C86A782
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