The code coverage in VistaDB continues to get better.  The graph below shows the percentage of coverage by namespace for the past ten months or so.  I generated this in Excel, I wish there was a code coverage tool that could generate this type of report. I am very pleased with our progress at getting automated tests for all of the code.  We have just hit 65% coverage for the entire engine.  Our goal is to reach 80% by the 1 year anniversary of 3.0 (April).  This is pretty amazing considering there were zero tests when 3.0 was released.  The current NUnit suites consists of over 525 public tests.  Internally we are going to start breaking up the NUnit tests to be categorized by the test type.  It takes too long to run all of them after every build on your workstation, the server should be doing that nightly anyway.  What I really want is the quick test that each programmer can run after any code change by category.  If you were working on the DDA Code just run the DDA tests quickly while working.  Then run the full workstation test suite at the end of the day. Here are some interesting metrics about the VistaDB Engine.

• Files: 109
• Classes: 808
• Functions: 6,952
• Total Sequence Points: 39,976

New version of NCover and NCoverExplorer On a side note there is new commercial only version of NCover and the NCoverExplorer applications.  Read more on the NCover blog.  The pricing starts at $149 for the pro version without a subscription ($99 extra).  The Enterprise version is $299 (+$149 1 year subscription).  I am running a trial version of the latest 2.x build right now.  I don't see that many differences from the older (and free) 1.x versions.  I think the NUnit team have a great product that definately fills a much needed tool in every serious programmers belt. Here is the screenshot of the current NCover report.

EDIT - The way you generate the graph with the namepsaces and % complete is to use the NCover Explorer application.  It is an HTML Report you can generate from there.  I don't know of a way to generate it from the command line.