Thoughts on NUnit and MSTest

I recently had a discussion with some other developers about NUnit and MSTest. My personal preference is based on familiarity -- originally from JUnit and TestNG, but also with NUnit. NUnit was around long before MSTest, and MSTest was not available with Visual Studio Express. I personally, haven't used MSTest so I scoured the internet … Continue reading Thoughts on NUnit and MSTest


Running NUnit tests programmatically

I'm working on a test framework that needs to be run by less-technical testers. The tests are data driven from a spreadsheet (google docs spreadsheet API + gdata.) Tests will be run locally (for now at least) since there isn't a test lab available for remote execution, and no CI. I didn't want to have … Continue reading Running NUnit tests programmatically

Links: Unit Testing and Continous Integration with Flex and AsUnit

Just a bunch of links to tutorials on using AsUnit and continuous integration with Flex Projects: A post on AsUnit by one of it's creators,  Luke Baye's: An example of a simple TestRunner mxml (AS2): Luke's post on continous integration: A good tutorial about using AsUnit (but with only a Flash testRunner): … Continue reading Links: Unit Testing and Continous Integration with Flex and AsUnit


A developer taught me about an interesting tool I never know about. jconsole is a gui app that comes with the JVM that can monitor memory usage of your java applications, threads, classes, and mbeans. By invoking your JVM with the following flags you can get all kinds of interesting information from %JAVA_HOME%/bin/jconsole.exe

The trouble with Blogs, Wikis, and Forums

There are a lot of great tools out there for blogging, wikis, and forums. Some of them even look nice and are (somewhat) friendly to use. I like wordpress, I like blogger, I like phpBB (except for the appearance), punBB, and others forum tools. I like wikis quite a lot. I've tried a lot of … Continue reading The trouble with Blogs, Wikis, and Forums

The trouble with CMS frameworks

My last post was about the trouble with MVC frameworks, in my view, which briefly is: Multiple action handling Component/Template processing (related to the above) Front controller/Back controller, helpers and the associated bloat or complexity and code duplication. I noted that CMS frameworks attempt to handle some of this, most especially the component/template paradigm -- … Continue reading The trouble with CMS frameworks

Modeling Products and Projects

I think many PM tools suffer from the problem of conflating multiple domain models, most likely in the attempt to shoehorm them into the same tool The simple PM tools I talked about (and reviewed previously) suffer from the additional problem oversimplifying, and provide inadequate domain elements to really model the process. I've come up … Continue reading Modeling Products and Projects

Thinking about development and related processes

In my mind, product development is broken down into three stages:  design, development, and deployment.  Project management and quality assurance are supplementary activities.  Project management manages scheduling, budget, resources (people and things) and tasks.  Quality Assurance is  responsible for testing, process, and requirements management.  In general, PM interfaces with "Business", and QA is concerned about … Continue reading Thinking about development and related processes

Model Hierarchies

Hierarchy complexity Hierarchies should be 4-7 levels deep. Three or less is not really a model.  Ten or more is too complex. Two levels is really just a tuple.  Three levels is is just grouping of tuples, which doesn't really require modeling.  Of course there are exceptions. Artificial Hierarchies You often see models (especially in … Continue reading Model Hierarchies

Guidelines for domain modeling

I think two common mistakes are made in modeling data & processes that can lead to unintended complexity.  The first is conflating two models that should be separate, and the second is oversimplifying models.Conflated model: when what should be two separate models are intermingled, resulting in confusing (forced) associations.  If you have two elements in … Continue reading Guidelines for domain modeling