Friday, June 21, 2002

.NETUnit If anyone is doing unit testing in .NET and is looking for an alternative to NUnit, you might want to check out my .NETUnit and MetaUnit Framework libraries. My framework takes a different approach to writing test suites, cases and methods. First of all it's completely declaritive, requiring you to do nothing but mark your fixtures and methods with attributes as opposed to the J/NUnit approach of subclassing TestCase and prefixing your methods with "test". It also follows a stricter definition of what a test case should be, which I've describe here. I don't have the rich UI for executing test suites yet, but I've supplied a command line sample. It's pretty straight forward and while I haven't worked on it recently, I do plan to pick it back up soon. Please feel free to post bugs, leave comments, and request features at the project's homepage. [Drew's Blog] 6:31:08 PM     Big props to Drew. I ran into the same error described by Drew in this post . Same "Failed to enable constraints" message. Thanks to Drew for having put in 4 hours on this. It saved me a ton of clueless frustration (the worst kind). My solution turned out to be a property setting on a Datatable. The setting was columns.Add(USERID_FLD, typeof(System.Int32)).AllowDBNull=false; The setting seemed innocent enough. It refers to a foreign key field from the db which was set to not allow Nulls at the db level. My code errored out at runtime. Only after I removed the AllowDBNull property did it execute without complaints. That was very odd. 6:14:19 PM

© Copyright 2004 Thomas Wagner. Last update: 5/2/2004; 4:44:44 PM. This theme is based on the SoundWaves (blue) Manila theme.