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

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025