0
-- provide test::unit agnostic api - mockery/context type objects on which the user must call setup/teardown?
0
+- maybe remove redundant require 'test_help' from init.rb - see mocha mailing list thread with subject "SslRequirements plugin and mocha"
0
+- update RELEASE file for all releases after 0.3.0
0
+- why does gem rdoc include all source files? what about other package types?
0
+- why does zip include Rakefile? what about other package types?
0
+- automate releases cf rspec
0
+- continuous integration build
0
+=> restrict partial mocks to existing public methods?
0
+- allow specification of class to be mocked, so we can check for existence of methods
0
+- investigate where/why check for existence of stubbed method has gone.
0
+- allow stubbing of private/protected methods? - force_stub?
0
+=> multiple expectations for same method
0
+- look at JMock for examples of when multiple expectations match
0
- increment actual count for ANY expectation that matches - see email from Bryan Helmkamp
0
-- add multiyield - see email from Jay Fields
0
- think about allowing a stubbing expectation to be converted to an asserting expectation and vice versa
0
- fail fast if expectation count exceeded during test...? c.f. JMock?
0
-- object methods needed for mocha itself should be aliased to __xx__ versions
0
-- maybe introduce blank_mock() and blank_stub() methods or make Stub include Object methods and Mock not...?
0
-- read and improve tutorial emailed by user
0
+- think about behaviour when more than one expectation/stubbed method match c.f. JMock?
0
+=> reduce footprint of mocha in terms of visible methods
0
+- do away with __is_a__ method if possible - Proc param may no longer be needed
0
+- add similar test to test_should_be_able_to_mock_standard_object_methods for partial mocks - rename non-public method with underscores e.g. mocha, reset_mocha, stubba_method, stubba_object, etc.
0
- reduce number of methods added to Object, Class etc to bare minimum
0
- reduce number of methods excluded from undef in mock_methods (maybe use blank_slate as mocha parent class to allow mocking of standard object methods?)
0
-- should we get two errors when unexpected method is called and similar expectation is not fulfilled? i.e. should we raise error in teardown if one has already been raised in test?
0
+- perhaps only add methods to particular class at point where expects or stubs gets called
0
+- provide some means to un-stubba an object - ideally should restore any methods with same names as stubba methods c.f. dealing with expectations for methods called :expects, :stubs, etc.
0
+- use Object#inspect(:mocha) or Object#__inspect__ instead of Object#mocha_inspect?
0
+- use builder object c.f. JMock
0
+- possibly simplify by making mock the same as a partial mock of Object
0
+- provide test::unit agnostic api - mockery/context type objects on which the user must call setup/teardown?
0
+- allow stubs/expects methods to accept method names as strings and symbols to retain similarity to define_method() et al
0
+- read and improve tutorial emailed by user
0
- default mock names to mock1, mock2, etc or something similar
0
- stubba mocks should named according to parent stubbee
0
-- allow specification of class to be mocked so we can check for existence of methods
0
-- allow stubbing of private/protected methods? - force_stub?
0
-- allow hash parameter for stubs and expects methods particularly for stubba
0
- use real activerecord as svn external to for testing instead of active_record_test_case
0
-- provide some means to un-stubba an object - ideally should restore any methods with same names as stubba methods c.f. dealing with expectations for methods called :expects, :stubs, etc.
0
-- automate releases cf rspec
0
-- think about behaviour when more than one expectation/stubbed method match c.f. JMock?
0
-- make verify method private (makes this unnecessary - fail if attempt to verify stub)
0
- test for setting expectations on class methods (and instance methods?) from within TestCase#setup
0
-- use Object#inspect(:mocha) or Object#__inspect__ instead of Object#mocha_inspect?
0
-- should all instances share expectations for any_instance or should each instance have their own - in which case how do we provide access to the instances
0
-- detect existing or added definition of mocha methods e.g. expects and alias to __expects?
0
+=> possible extra functionality
0
+- add multiyield - see email from Jay Fields
0
+- allow hash parameter for stubs and expects methods particularly for stubba
0
- more jmock style stuff - e.g. labels/required order, more sophisticated param matching?
0
-- stubs should only return a fixed value - no blocks allowed for return values and no parameter expectations allowed?
0
-- maybe allow unstubbing of a specific method from within a test...?
0
\ No newline at end of file
0
+- maybe allow unstubbing of a specific method from within a test...?
0
+- should all instances share expectations for any_instance or should each instance have their own - in which case how do we provide access to the instances
0
\ No newline at end of file
) is private.
