I'm dusting off a Script Builder application I've done as an addin to Visual Studio 2002 and 2003. The application takes an XML description of a SourceSafe repository and appends all the scripts together in one file. The XML format allows for complete control over order and exclusions. This is currently used to install/upgrade database installations - but it could be used to concatenate any type of text files. I'm adding the ability to run from a command prompt as part of VS build and completely removed from the VS environment.
My next step is to build/buy a tool that integrates with an installation to automate the running of the script on the target database. I may need to run the script on multiple servers at a given site - so I'm ideally looking for a way to store this information on site so I don't have to remember each server location/login each time.
Hopefully I can find a tool like this. I'll post what I find...
This weekend I started writing testing code under NUnit for the .Math project. Now I know this approach is completely backward, the original product was written in '97 and development didn't proceed using TDD/Agile methods. However, I think the long-term quality of a product with the flexibility of a compiler can benefit from a testing set. This, of course, allows for a full test of the capabilities after making any mods/feature additions/bug fixes.
I'm starting with a backward approach - I realize this and it's unfortunate but a reality of the product state. I'm first testing the compilation results to make certain each function and operator is being evaluated properly. Then I'll drill down into the individual areas of the application - the parser, the support classes, etc.. I'll post the test code on the download site when it's available.
I think this is the only way I can certify a release as complete. This way anyone can grab the test suite and see the compiler is capable of performing the promised tasks. I got the idea from the NUnit site. I really like their Coding Standards stating:
“Test-Driven Development. This is non-negotiable. There will be no code that is accepted without associated tests. Also, we expect that Refactoring is part of your everyday activities so if there is a need to refactor do it.”
Bottom line, I believe that software quality is a reflection of the developer. I think a TDD set is reasonable a way I can be confident in telling others the product is ready to be called a non-beta release.
I debated blogging this entry until I read George Will's article on President Reagan's legacy.
“One measure of a leader's greatness is this: By the time he dies the dangers that summoned him to greatness have been so thoroughly defeated, in no small measure by what he did, it is difficult to recall the magnitude of those dangers, or of his achievements. So if you seek Ronald Reagan's monument, look around, and consider what you do not see.” - George Will