Blog

TestBox BDD/xUnit Testing v1.1.0 Final

Luis Majano February 12, 2014

Spread the word

Luis Majano

February 12, 2014

Spread the word


Share your thoughts

We are very happy to release our first minor patch for TestBox.  This update includes finalizations of some features but mostly tons and tons of improvements and fixes as our library matures.  For those of you who do not know about TestBox, TestBox is a next generation testing framework for ColdFusion (CFML) that is based on BDD (Behavior Driven Development) for providing a clean obvious syntax for writing tests.

It contains not only a testing framework, runner, assertions and expectations library but also integrates with MockBox for mocking and stubbing. It also supports xUnit style of testing and MXUnit compatibilities.  TestBox can be downloaded from our main downloads page and it has been also integrated into the ColdBox platform as well.

Release Notes

Bugs

  • [TESTBOX-43] - Test case names in xUnit have better definitions
  • [TESTBOX-44] - Output and mode arguments not compat with MXUnit's HTML formats
  • [TESTBOX-45] - isExpectedException fails on non-inherited specs
  • [TESTBOX-46] - ANTJunit reporter needs to build single tree suite instead of nested suites
  • [TESTBOX-51] - Some MXUnit extension assertions are missing
  • [TESTBOX-53] - makePublic() doesn't seem to work for packaged methods on compatibility mode
  • [TESTBOX-54] - mock(), getMockFactory(), setMockingframework() not implemented
  • [TESTBOX-56] - The method init was not found in component TestCase.cfc.
  • [TESTBOX-58] - toThrow() cannot match empty message & cannot match detail
  • [TESTBOX-59] - isEqual assertion returns false with two equal complex structures or arrays
  • [TESTBOX-60] - HTTP Runner in samples errors
  • [TESTBOX-61] - Samples will not run without ColdBox
  • [TESTBOX-63] - beforeEach does not fire in recursive fashion for nested suites
  • [TESTBOX-65] - expectException() doesn't work on certain use cases with annotations and method calls.
  • [TESTBOX-67] - directoryTestSuite.run() doesn't completely respect its "excludes" argument in compat mode
  • [TESTBOX-68] - TestCase.cfc doesn't have life-cycle methods on compat mode
  • [TESTBOX-71] - "Global Stats" summary does not include failures from "Global Bundle Exception" failures
  • [TESTBOX-72] - Nested empty describe blocks don't show in runner

Improvement

  • [TESTBOX-57] - Allow building of ant.properties file for ANT runner so build can fail
  • [TESTBOX-70] - Reporters improved to allow for better UI when skipping and excluding tests

Resources

Finally, TestBox is also a direct drop-replacement for MXUnit as well.  

Add Your Comment

Recent Entries

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

At Ortus Solutions, we’ve always been at the forefront of innovation in the ColdFusion ecosystem. From pioneering modern ColdFusion practices to developing cutting-edge tools and frameworks, we’ve been passionate to help and sup[port the community into shaping the future of web development.That’s why we decided to build BoxLang, our new JVM programming language that not only builds on the strengths of ColdFusion but takes modern software development to the next level.

Maria Jose Herrera
Maria Jose Herrera
December 23, 2024
Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

As we approach a stable release of BoxLang and our continued marketing reaches more folks, many have asked about its purpose. Why create a new language when the JVM ecosystem already includes established languages like Kotlin, Groovy, and Scala, to name a few.

Luis Majano
Luis Majano
December 18, 2024