Result for 24C9F5C398DE0777985C3113DA1648201331DA1A

Query result

Key Value
FileName./usr/share/doc/python-fudge-doc/html/_sources/api/fudge.inspector.rst.txt
FileSize216
MD55F26E8A03FBDF7E590D1BBD3D4813189
SHA-124C9F5C398DE0777985C3113DA1648201331DA1A
SHA-256AD8392D720BEB0F7F759DC962B4ABC42500DE5488389529A8F956A5033EAA6A4
SSDEEP3:E0DbDVKGpKJV7CEKe/E/VHEyHOAGHvBKe/E/VfKRzFHOAGt66Txvn:E0DsGpQkEjE/ehjE/oL2xv
TLSHT1F8D0120A1F432CA1906FC874E3690062E24083FFCC2603A8042C0501FE48C655FDDBC2
hashlookup:parent-total8
hashlookup:trust90

Network graph view

Parents (Total: 8)

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

Key Value
FileSize45640
MD5203FFD078EC5604FDDCAAF4192B621EC
PackageDescriptionPython module for using fake objects for tests, documentation package 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. . Fudge was inspired by Mocha which is a simpler version of jMock. But unlike Mocha, Fudge does not automatically hijack real objects; you explicitly patch them in your test. And unlike jMock, Fudge is only as strict about expectations as you want it to be. If the type of arguments sent to the fake method aren’t important then you don’t have to declare an expectation for them. . This is the documentation of python-fudge.
PackageMaintainerDebian Python Modules Team <python-modules-team@lists.alioth.debian.org>
PackageNamepython-fudge-doc
PackageSectiondoc
PackageVersion1.1.0-1
SHA-1B56BA13B821DA3E5E336ECABFFEDF0365832F7B6
SHA-25602F77C93476805D721E39D47A45C11792DFD6355B217D09CC1EC22911BC26843
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
Key Value
FileSize45828
MD545B1585C4297BC45904D47191014E4C7
PackageDescriptionPython module for using fake objects for tests, documentation package 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. . Fudge was inspired by Mocha which is a simpler version of jMock. But unlike Mocha, Fudge does not automatically hijack real objects; you explicitly patch them in your test. And unlike jMock, Fudge is only as strict about expectations as you want it to be. If the type of arguments sent to the fake method aren’t important then you don’t have to declare an expectation for them. . This is the documentation of python-fudge.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-fudge-doc
PackageSectiondoc
PackageVersion1.1.0-1
SHA-197B1DBC8B151D99BDD8C91031F1343E054890CA9
SHA-25600B92CC4A413CF8501D5A4BCCA15C48EC59361F67EF2046507194B51853B4C06
Key Value
FileSize31912
MD5072BE819CDAB7C486DDDFCE728DB0DCF
PackageDescriptionPython module for using fake objects for tests, documentation package 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. . Fudge was inspired by Mocha which is a simpler version of jMock. But unlike Mocha, Fudge does not automatically hijack real objects; you explicitly patch them in your test. And unlike jMock, Fudge is only as strict about expectations as you want it to be. If the type of arguments sent to the fake method aren’t important then you don’t have to declare an expectation for them. . This is the documentation of python-fudge.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-fudge-doc
PackageSectiondoc
PackageVersion1.1.0-2
SHA-1696EA7C2EC08EE6EAE1724A279C693E7E17D8F67
SHA-25609E1A767E64472BFD15EEEAF9EC43A67B253CE5B9628B026CB7E96C59BD8129A
Key Value
FileSize31872
MD53A8814D907EC961081AFF778CBF9DEB0
PackageDescriptionPython module for using fake objects for tests, documentation package 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. . Fudge was inspired by Mocha which is a simpler version of jMock. But unlike Mocha, Fudge does not automatically hijack real objects; you explicitly patch them in your test. And unlike jMock, Fudge is only as strict about expectations as you want it to be. If the type of arguments sent to the fake method aren’t important then you don’t have to declare an expectation for them. . This is the documentation of python-fudge.
PackageMaintainerDebian Python Modules Team <python-modules-team@lists.alioth.debian.org>
PackageNamepython-fudge-doc
PackageSectiondoc
PackageVersion1.1.0-2
SHA-1F808B42B57C15A726DBC543E12C010B1CA9A74E2
SHA-256EFA92E8CC35A0BEBF9580F191D014D923C292C038CC1E6974286B07B1F3BFFCD
Key Value
MD592853F165708E5D7EECA14B7D8541083
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
PackageNamepython3-fudge
PackageReleaselp151.3.3
PackageVersion1.1.0
SHA-16287D59D3391A74BCF35726C076AAE260C355BB6
SHA-25628902D830074136F2097629534F0F255D84C84768DFF169B619EDDB1EA3CDC46
Key Value
MD5E8EC2EB8384953FCACCA767DC090C966
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
PackageNamepython3-fudge
PackageReleaselp150.2.3
PackageVersion1.1.0
SHA-17D07BA05C9B6062E440AA47BC15FD79A3F3A9998
SHA-256A4EC66DB5E1F3F6D77589FA9604A7BF2E66DDBC051F8D3C867D50CFDDC122A73