Phake 2.1.0 is now released

New Features

#158 – Allow direct calling of protected methods for mocks
Allow for calling of private and protected methods on mocks using new Phake::makeVisible() and Phake::makeStaticsVisible() wrappers. This will allow for slightly easier testing of legacy code and abstracts.


#178 – Renamed thenGetReturnByLambda to thenReturnCallback
The thenGetReturnByLambda just didn’t quite sound right and was difficult to remember so we changed the name. While the original method will still work, a deprecation error will be emitted by the code when thenGetReturnByLambda is called with a message that you should use thenReturnCallback instead. The great news is that no other project in their right mind would ever use that method name, so a search and replace should be pretty reliable.

#144 – Improve Phake::verify error message
When a method doesn’t match you will now be given a more appropriate diff as to why. This should help make life a little easier when debugging failing tests.

Enhanced integration with Travis-CI
We are now testing all the things!

Integrated with Scrutenizer
We are also measuring all the things


Phake 2.0.0 RC 1 released

I just finished updated documentation for the last of the more recent set of features for Phake. It’s been a long time coming but I am fairly certain 2.0.0 is ready for release. I have a handful more changes I am planning on making but they can come in 2.1.

I would be curious to get feedback from anyone already using Phake. If I get good feedback (or no feedback) I will roll it out as stable later on this week. If you aren’t sure what Phake is then you can read the Phake documentation or browse the Phake GitHub repo.

The summary of it is that it is a mock testing framework that aims to allow you to test mocks using more assert like behavior which allows for more consistent and (in my opinion) easier to understand test structure. It has a few nifty features like argument capturing and reference parameter setting in stubs.