Smoketest 2.0.3 Update
[Estimated Reading Time: 5 minutes] An overview of the changes in Smoketest 2.0.3 including Setup/Teardown methods and improved formatting of console output.
Introducing: Smoketest 2.0
[Estimated Reading Time: 6 minutes] Meet the new Smoketest. Nothing like the old Smoketest. A new, ultra-lightweight unit testing framework with xUnit 2.x result output (and the ability to support other output formats as needed).
Smoketest – Set Me Up / Tear Me Down
[Estimated Reading Time: 3 minutes] In a previous post I demonstrated how the default “pretty name” for a Smoketest test case (derived from the test case classname) can be over-ridden by a test developer by implementing a specific interface (INameCase) on the test case class itself. There are some other interfaces that can be implemented on a test case, including interfaces that allow a test case to implement housekeeping tasks for the tests it provides.
Smoketest – Some Differences With DUnit
[Estimated Reading Time: 6 minutes] Writing tests in Smoketest is intended to enable a test developer to write tests in a way that describe themselves, without requiring the test developer to add this “narrative” themselves. To see this in action, I thought I would compare some simple DUnit tests with the equivalent using the Smoketest framework.
Thinking Creatively with QueryInterface()
[Estimated Reading Time: 4 minutes] I soon hope to be releasing “Smoketest”, a testing framework that I have developed over the past few years. It has actually been in production use for most of that time (albeit by my own good self) but also continues to develop and evolve. On the occasions when I have mentioned it, people have asked me to publish it, but I have been reluctant to do so up to now for a number of reasons, not least that it needs a bit of polishing to make it suitable for public scrutiny.
Exchange() – Epilogue and Smoketest
[Estimated Reading Time: 5 minutes] A colleague of mine directed me to a further minor refinement of the ‘final’ Exchange() code I posted the other day. The change is minor but yields a worthwhile performance improvement, but my main reason for bothering to post (yet!) another update is an excuse to introduce the testing framework I developed that allowed me to quickly assess any benefit.