A new friend of mine wants to collaborate on building a new .NET based testing framework. I know, I know, there are plenty of testing frameworks out there. Just to name a few: NUnit, MbUnit, xUnit.NET, nSpec, etc. Each of these has their own strengths, weaknesses, and implicit/explicit testing methodologies associated with them. So why would I bother saturating the market further with another testing framework?
I think I have a semi-unique idea. I say “semi”, because the underlying design idea is applied in other technology areas, but it would be unique in its application to testing. I think it’s has enough of a fundamental difference from all of the existing testing frameworks to justify building it. A by-product of the design would mean that it would be mostly compatible with existing testing frameworks (and in fact I would try hard to maintain that quality, but not in all scenarios), but would also open up avenues for experimenting with new ways to represent tests.
So, the reason for this post (besides encouraging a barrage of people telling me not to put yet-another-testing-framework out there) – what do you think is missing from testing frameworks today that you would like to see in the future?