CaptureMock 1.0

Milestone information

Project:
CaptureMock
Series:
trunk
Version:
1.0
Released:
2014-04-03  
Registrant:
Geoff Bache
Release registered:
2014-04-03
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon CaptureMock-1.0.tar.gz (md5) Code 71
last downloaded 14 weeks ago
Total downloads: 71

Release notes 

Enhancements:

    - Supports python callbacks in a limited fashion (i.e. intercepted code calling back into non-intercepted code)
 Indented syntax for this. Makes it possible to e.g. intercept Tkinter and use CaptureMock for a limited kind of GUI
 testing.
    - Should work better in Python 3
    - Naming of "variables" is more intelligent and descriptive, make use of strings provided when the objects first appear
    - Mock files are more readable, we use pprint to ensure it doesn't get too wide
    - Client-server support now handles XMLRPC servers

Changelog 

View the full changelog

Enhancements:

    - Supports python callbacks in a limited fashion (i.e. intercepted code calling back into non-intercepted code)
 Indented syntax for this. Makes it possible to e.g. intercept Tkinter and use CaptureMock for a limited kind of GUI
 testing.
    - Should work better in Python 3
    - Naming of "variables" is more intelligent and descriptive, make use of strings provided when the objects first appear
    - Mock files are more readable, we use pprint to ensure it doesn't get too wide
    - Client-server support now handles XMLRPC servers

Bugfixes:
    (Python)
    - Don't overwrite sys.meta_path, should work better with py.test (Thanks Marc Abramowitz)
    - Fixing custom metaclass issues in https://bugs.launchpad.net/capturemock/+bug/1256218 (Thanks Marc Abramowitz)
    - Callstack checking, and hence not recording stuff used from the standard library, should work better in virtual
 environments now
    - Supports use of Abstract Base Classes, i.e. collections.MutableMapping etc
    - Does not fail on classes named Instance
    - Handle multiline strings starting with a '
    - Handle exceptions raised by constructors properly
    - Handle standard iterators produced by custom lists
    - Fixed bug with attributes of list objects (Thanks Marc Abramowitz again)
    - Special handling of __file__, it rarely makes sense to record this
    - Making mixed mode more useful for Python attributes: use any replay info which matches at least function names
    - Don't repeat base class descriptions unnecessarily
    - Don't leak temporary files if exceptions are thrown
    - Improve handling of very deep inheritance structures
    - Handle subclasses of immutable types like int
    - Handle multiline strings in lists
    - Handle submodules imported via other packages
    - Handle __nonzero__ methods properly (Thanks Lars Stavholm)
    - Handle exceptions thrown by __dir__ methods
    - Better handling of repeated references to the same attribute when replaying
    - Trying to handle side-effect assignments properly, notice when their value changes
    (Command line)
    - If the same location is added several times to e.g. PATH, only mention it once in command line calls.
    - Preventing server crashes if file edits are found more than once
    - File edits now treat environment variables the same way as command line options, and hence find more files
    - File edits are more threadsafe, simultaneous edits should not interfere
    - Handle edits that turn a link into a directory
    - Fixing diagnostic related problems if no logging.conf exists
    (Client-Server)
    - Client responses are returned in order, not using matching

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.