Key | Value |
---|---|
FileName | ./usr/lib/python2.7/dist-packages/fudge/tests/test_inspector.py |
FileSize | 8732 |
MD5 | 28C701B1A7E04DB5E5DD33B760017612 |
SHA-1 | 12C226FB74C5492155F95D85198220CB6F7C96C2 |
SHA-256 | EBC1380EE7EB7E62B5D67E17D589F1BE84FB4B88B10C6806041B373B3726C22D |
SSDEEP | 192:tBEDf02z9q+qmsjXSXYmvx1AyHVB823kEcNejf6NA:tBEDXlZIiXxv7r623kEcNEAA |
TLSH | T1F802B23893234D79E74BC47488A3E5036F1DF5978888197CF6FC90819FA8524C6D96AE |
hashlookup:parent-total | 4 |
hashlookup:trust | 70 |
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 28740 |
MD5 | CD6184DDFED767F437740E0FC2899CB2 |
PackageDescription | Python 2 module for using fake objects for tests 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 Python 2 version of the package. |
PackageMaintainer | Debian Python Modules Team <python-modules-team@lists.alioth.debian.org> |
PackageName | python-fudge |
PackageSection | python |
PackageVersion | 1.1.0-1 |
SHA-1 | 6B00A2BE175AB4E4D9A828399B81BFD6148BC0F4 |
SHA-256 | C4A14D6B4092709ABFC637C46F874C8C9F6B83A0873ED0824159782D9CFDAED8 |
Key | Value |
---|---|
FileSize | 28826 |
MD5 | 39794530BFD54367DD07B66DE698F54F |
PackageDescription | Python 2 module for using fake objects for tests 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 Python 2 version of the package. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-fudge |
PackageSection | python |
PackageVersion | 1.1.0-1 |
SHA-1 | 11273780AD6E2450256888E790FFFDF978E62850 |
SHA-256 | 2F794465437F5CA9D8627706B2681C721CE4166EF0A6C482A306EAEA990A55E2 |
Key | Value |
---|---|
MD5 | 5B8785CBEEF93AF07A9448E5816373BA |
PackageArch | noarch |
PackageDescription | Complete 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() |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-fudge |
PackageRelease | lp150.2.3 |
PackageVersion | 1.1.0 |
SHA-1 | 60DC069A7E153DB3A9A044E2B44D3BFC28881AAF |
SHA-256 | 3BF09D5211E6497B12EA7F1A764E47AE156FA6706799D8897E1C715D063D6597 |
Key | Value |
---|---|
MD5 | F5B77D1E78BC753A82C6DBD848B9E46B |
PackageArch | noarch |
PackageDescription | Complete 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() |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-fudge |
PackageRelease | lp151.3.3 |
PackageVersion | 1.1.0 |
SHA-1 | 18C8621522567E66C64891038C9AF50C1E61A076 |
SHA-256 | D83F07C4246563D3C12989FD6105B47E079349DC5071D4CC8027A6A50E695344 |