Blog

MockBox 1.3 Released

Luis Majano December 12, 2010

Spread the word

Luis Majano

December 12, 2010

Spread the word


Share your thoughts

After much inspiration during long baby duty nights, we bring you today MockBox version 1.3.  This release sports a revamp of the entire documentation structure both on the wiki and internally in the API.  This was a huge ticket for me, as I wanted to make the introduction into mocking and unit testing a little bit easier.  So hopefully, this will help out all you curious folks who want to venture down into MockLand!  So let's review it:

So we already said the documentation and API docs are brand new, great! So what else:
  • coldbox-1057 mocking argument normalization, diff expectations when name-value or positional argument calling.  This means that you can test with ordered or name-value pairs or even argument collections and MockBox will determine the right matching values for you.  If you are new to MockBox, don't worry, this was a cool fix to how MockBox matches arguments to results.
  • coldbox-1144 change all mock methods to their $ name equivalents on the MockBox CFC so they are documented like so.  This was not the case on version 1.2 where we created method aliases, this just added overhead and not a very clear mocking API.  So this was revamped and I documented the functions out of it.

New Verification Methods


Unit testing and mocking cannot be possible without behavior verification, so we expanded our mocking language to include several new methods to help you verify when these mocked methods are called.  Also remember that MockBox has call logging integrated so it can keep track of method calls and their real arguments, so you can assert them later via the $callLog() method.


$verifyCallCount becomes $times()


This is just an alias, but it is way shorter and more meaningful, which basically let's you find out how many times ALL mocked methods have been called on a target, or if you pass in the method name as an argument, then only the times that specific method was called.


$atMost() and $atLeast()



These verification methods allow you to track the minimum and maximum times ALL mocked methods have been called or if you pass in the method name, the specific method.  This is great to achieve minimum number or maximum number of calls to a specific method have to be made and then asserted.


$never() and $once()


These are great shortcuts to find out if a mocked method or ALL mocked methods have NEVER been called or they have been called exactly one time.


$reset()


This little gem provides you with a way to reset all method call counter and call loggers so you can start fresh and mock again!


This concludes our 1.3 release. We have lots of great ideas for our next version MockBox 2.0 which will includes some awesomeness when it comes down to expectations, verifications and behavior. We are already planning several features that will allow you to verify when methods with specific arguments have been called, create literal arguments instead of data, mock network failures and much more. So get ready to start working in MockLand, it truly is great to Mock!

Add Your Comment

Recent Entries

BoxLang 1.0.0 Beta 23 Launched

BoxLang 1.0.0 Beta 23 Launched

The latest release of BoxLang, Beta 23, marks a significant step forward in our journey to create the ultimate dynamic language for the JVM. Packed with powerful new features, important bug fixes, and thoughtful optimizations, this update is designed to make your development experience smoother, faster, and more reliable, especially after now starting to take 100s of comments and bug reports from our community.

Luis Majano
Luis Majano
November 23, 2024
TestBox Latest Updates and News!

TestBox Latest Updates and News!

We’re thrilled to have launched the new TestBox website and TestBox 6.0! If you haven’t had a chance to explore yet, visit TestBox to discover updated documentation, powerful resources, and features that make testing more efficient than ever.

Maria Jose Herrera
Maria Jose Herrera
November 21, 2024
Is Your ColdFusion Application Ready for the Future?

Is Your ColdFusion Application Ready for the Future?

In a rapidly evolving digital world, maintaining performance, security, and scalability for ColdFusion applications is more challenging than ever. Whether you're using Lucee or Adobe ColdFusion, legacy systems can become a bottleneck for growth, innovation, and user satisfaction. The need to future-proof your ColdFusion applications has never been more critical.

But where do you start?


The Hidden Costs of an Outdated ColdFusion Application

As you...

Cristobal Escobar
Cristobal Escobar
November 21, 2024