Home/ Questions/Q 830119
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T03:59:30+00:00

A group of us (.NET developers) are talking unit testing. Not any one framework

  • 0

A group of us (.NET developers) are talking unit testing. Not any one framework (we’ve hit on MSpec, NUint, MSTest, RhinoMocks, TypeMock, etc) — we’re just talking generally.

We see lots of syntax that forces a distinct unit test per scenario, but we don’t see an avenue to re-using one unit test with various inputs or scenarios. Also, we don’t see an avenue to multiple asserts in a given test without an early assert’s failure threatening the testing of later asserts (in the same test).

Is there anything like that happening in .NET unit testing (state- or behavior-based) today?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    look at [TestCase(params)] in NUnit
    allows doing the same test with different inputs.

    also, for the multiple asserts thing,
    look at OAPT (One assert per test) runner – which promises to take a test with muliple asserts and run each assert as its own test:
    http://rauchy.net/oapt/

    • 0