I was recently working on NUnit tests and I found the current method of how NMaven handles unit testing inadequete. The problem occurs because C#'s protected method is accessible only within the defining class and its derived classes, unlike Java which includes package level access. NMaven currently compiles the test and main artifacts into separate assemblies, so I also can't test an internal method either. This leaves the ability of only testing public methods, which are a little too coarse grained for what I need. One option that I am considering is to 1) compile main artifact,; 2) compile test artifact, which includes both main and test classes. This would require compiling the main classes twice but would allow the testing of internal methods. I am not sure how people are building their .NET applications or whether this option would cause performance problems. Thoughts?
Shane
