python-fudge 1.0.3-3 source package in Ubuntu
Changelog
python-fudge (1.0.3-3) unstable; urgency=low
* Fix "missing dependency on python3!!" by using correct variable in
debian/control (Closes: #674405)
* fix Vcs-Svn and Vcs-Browser URLs in debian/control
-- Jan Dittberner <email address hidden> Thu, 24 May 2012 15:21:51 +0200
Upload details
- Uploaded by:
- Debian Python Modules Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Python Modules Team
- Architectures:
- all
- Section:
- python
- Urgency:
- Low Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Trusty | release | universe | python |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| python-fudge_1.0.3-3.dsc | 2.2 KiB | be83c676c6efce97983762aabd8cab839134592a3c8e82d40a1677681e9c1f76 |
| python-fudge_1.0.3.orig.tar.gz | 85.5 KiB | f8c8bfb3c0199dd06108c0c5a80e3645c7a071e0917b1a3bc73c761800809251 |
| python-fudge_1.0.3-3.debian.tar.gz | 2.9 KiB | 185bd2c87b6e55fe0ce9b497c9f62d5b8bb35e17e50ce56d550b6afe650e2820 |
Available diffs
- diff from 1.0.3-2 to 1.0.3-3 (895 bytes)
No changes file available.
Binary packages built by this source
- python-fudge: 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.
- python-fudge-doc: Python 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.
- python3-fudge: Python 3 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 3 version of the package.
