Griffin,
Please review the changes in branch RFE_1098585. They deal with
dynamically generating an implementation of ITestFramework on startup.
So far, I've written "stub makers" for NUnit and MbUnit.
If the assembly environment variable is empty, we look for
nunit.framework using Assembly.LoadWithPartialName(). If that fails we
try MbUnit.Core. Then we dynamically generate an implementation and
assign it to Assertion._testFramework.
I've got to clean it up a bit. Perhaps find some ways of getting better
test coverage. I've also got to implement the csUnit bindings. But you
can get an idea of where I'm going.
--Choy
|
