Blog

Luis Majano

May 18, 2017

Spread the word


Share your thoughts


We are excited to announce the release of TestBox version 2.5.0. To install just do:


box install testbox --savedev

To upgrade your current testbox installation just run the following:


box uninstall testbox && install testbox --savedev

TestBox 2.5.0 is a minor release with some great new functionality and tons of fixes. You can find the release notes here and the major updates for this release. One of the biggest features for TestBox that was not part of TestBox, was the addition of TestBox Watchers to CommandBox.

TestBox Watchers

CommandBox CLI has added watching capabilities to the testbox namespace. Which means you can now run the following command in the root of your project: testbox watch and it will monitor all your CFCs for changes. If a change is detected, then it will fire the new testbox run command with our CLI reporter.

Life-Cycle Data Binding

We had introduced spec data binding in TestBox for creating dynamic specs and passing dynamic data into them. We have extended this feature into life-cycle methods:

  • beforeEach()
  • afterEach()
  • aroundEach()

You can now pass in an argument called data which is a struct of dynamic data to pass into the life-cycle method. You can then pickup this data in the closure for the life-cycle. Here is a typical example:


describe( "Ability to bind data to life-cycle methods", function(){
	var data = [
		"spec1",
		"spec2"
	];

	for( var thisData in data ){
		describe( "Trying #thisData#", function(){
			beforeEach( data={ myData = thisData }, body=function( currentSpec, data ){
				targetData = arguments.data.myData;
			});
			it( title="should account for life-cycle data binding",
				data={ myData = thisData},
				body=function( data ){
				expect(	targetData ).toBe( data.mydata );
			}
	);

	afterEach( data={ myData = thisData }, body=function( currentSpec, data ){
		targetData = arguments.data.myData;
		});
	});
	}

	for( var thisData in data ){

		describe( "Trying around life-cycles with #thisData#", function(){
			aroundEach( data={ myData = thisData }, body = function( spec, suite, data ){
				targetData = arguments.data.myData;
				arguments.spec.body( data=arguments.spec.data );
			});

			it( title="should account for life-cycle data binding",
				data={ myData = thisData },
				body=function( data ){
				expect(	targetData ).toBe( data.mydata );
			}
			);
		});

	}
});

Release Notes

Bugs

  • [TESTBOX-177] - Simple reporter broken on Adobe servers
  • [TESTBOX-180] - HTML Runner links should include directory param
  • [TESTBOX-181] - AsyncAll Errroring on xUnit runner
  • [TESTBOX-183] - the 'type' argument was being ignored if the 'regex' argument was provided and matched the exception data

Improvements

  • [TESTBOX-178] - Remove thread scope from debug stream
  • [TESTBOX-184] - Passing Data to Dynamic Tests via life-cycle methods: around, after, before
  • [TESTBOX-185] - Preserve whitespace in HTML (simple) Reporter
  • [TESTBOX-186] - Include TestBox version in TestResult memento
  • [TESTBOX-187] - Let travis handle upload of api docs and snapshot binaries
  • [TESTBOX-188] - Aggregate suite stats from nested suties

Add Your Comment

Recent Entries

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Luis Majano
Luis Majano
March 13, 2026
Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

  • internal banking workflows
  • reporting systems
  • client portals
  • data integration platforms
  • compliance and risk management tools

In many cases, thes...

Cristobal Escobar
Cristobal Escobar
March 13, 2026
Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Cristobal Escobar
Cristobal Escobar
March 12, 2026