Not Fitnesse
Well, I've given up on installing Fitnesse locally. Despite installing the correct version of the JRE, I can't get it to run. I still believe that Fitnesse is a good tool that I'd like to play around with at some point, but not now, and not on this machine.
I can get away with something a little lighter anyway. I don't need the collaboration or the wiki, I just need a test driver. So, I'll just have to write one.
Build vs. Buy
Or possibly, just get one. There is a www.vbunit.org Unit-testing tool for VB. There is also aspunit.sourceforge.net ASPUnit, but it runs on top of IIS (which, upon reflection, it would have to do), which I don't have installed locally. Really, most of the problems I'm encountering are of my own creation - upgrading my machine would go a long way to solving them.
So far, my choices are: (a) write a local ASP test driver, or (b) install and use VBUnit, code a bunch of DLLs with the "business" (read "gaming") logic, and deploy most of the code as binary files. This second approach has the advantage of separating the presentation layer, which is always nice, and leaves the components in a re-usable state. Let's head down that path.
Path Bee
First step, does my hosting provider let me deploy binary files? *Research* No. I should note that there is another option (c) write it in ASP.Net. For now, back to Path A.
Path Eh
So, the idea is that I'm going to set up a web project, create a simple ASP class (to simulate the roll a die - important in an RPG like game), and create a test harness. First, though, time for a break.
posted by FlyingSheep @ 3:28 PM
2 Comments:
don't give up, fitnesse is a great tool. As far as I can tell, you want to use it to test .net code (mentioning vbunit and aspunit) - the default distribution comes with .Net 1.1 binaries, which might have been the problem why it did not work. I wrote a short guide on how to get started with FitNesse and .Net - you can find solutions for other common problems in that document. Download it from http://gojko.net/fitnesse
Thanks for the encouragement (:
Unfortunately, I'm not using .Net code, I'm writing this in "classic" ASP (VBScript).
I'd rather not simultaniously switch methodologies (from up-front design to test-driven development) AND switch languages (from ASP to C#.Net). As such, I've chosen to stick with just changing methodologies for this project (next project will be in C#.Net most likely).
Now, this decision has not been without pain, as some refactorings (particularlly those making use of polymorphism) are not available to me. But please bear with me. You can take a look at my current progress (my list of tests) here. You'll probably see one or two failing tests, which represent my current work.
Post a Comment
<< Home