#2234: have a better-defined approach to mocking
------------------------+---------------------
Reporter: dustin | Owner: dustin
Type: enhancement | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.8.5 | Resolution:
Keywords: tests |
------------------------+---------------------
Comment (by dustin):
There's no problem with mocking third-party objects -- in fact, that's the
"normal" use of mocks. Synchronizing the mock and the API there has not
been problematic, and should be tested with integration tests.
Mock can do some introspection (and Foord announced that 0.8.0 has
"autospec", which makes it even easier). However, I'd like to check the
signatures directly, rather than relying on the tests to uncover any
inconsistencies by getting an error from mock. If practical, we can do
both!
--
Ticket URL: <http://trac.buildbot.net/ticket/2234#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
